-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question/Bug : mount error 32 #1308
Comments
@DeuxCatPotes Hi \o can you share output for following commands?
Also, as I see that you are using Centos 7.9, I expect you are using downstream modification of leapp-repository - Elevate. I am aware they have several modifications so I cannot be sure whether we could reproduce this at all. In case that you are using Elevate, I suggest you to contact the vendor for the help also. If I try to make a blind shot, I do not think it's a space problem. I would check any "non-standard" mount options as we are aware of some issues around that. I would check whether there is any system log that could explain what happened (selinux?). As you have the backtrace, I would try to add a breakpoint into the code to pause the execution of the related actor when the problem happens, so all created files (e.g. disk images) would be still present on the disk and you could try to experiment with the mount operation outside of leapp. Also I suggest to check during the execution of leapp e.g. number of opened files. I would expect a different err msg in case of hitting some limits but I cannot rule out this possibility. Also I would be a little bit afraid of the persistent /tmp. I know it's possible to upgrade even having /tmp on a partition instead of having using tmpfs, but who knows 🤷 (from what I wrote above, I would give this a least significance as a possible root cause). Also check logs under /var/log/leapp/leapp-preupgrade.txt during the execution of the target_userspace_creator actor, whether there are not any suspicious warnings or command output before. |
Hi thx for feedback. I m not the guy who create that virtual machine. cat /etc/fstab
mount
rpm -qa 'leapp'
cat /etc/system-release
Can the nosuid prevent the upgrade ? I think not, previous vm migrated also had nosuid flags. Maybe i can try to setup a tmpfs ? Also that vm is not currently in centos 7 I already migrate it one time to ol7. At that day i already did more or less 10 vm without that issue. Hope you can help me @pirat89 , and thx for your time. |
Ok @pirat89 i think i find the root cause. I have to go but i will update tomorrrow for a proper feedback and maybe a better warning |
Hello computer sea friends, So what occurs during my try to upgrade. The current not working step is a mount loop step (as log show).
I think a test can be done to check the current value :
or
A grep can also display clue about where the value is set. thx for your time. |
@DeuxCatPotes thank you for the investigation of the issue! I think that it makes sense to check the value on failed mount or at least add a suggestion to the error msg for user to check the value as a possible root cause. I am keeping the issue opened to cover it. |
When i try to preupgrade :
Some other information :
I do not understand what can make that issue occur ? My best option is missing space somewhere ?
The text was updated successfully, but these errors were encountered: