Skip to content
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

Is there a reason why the option is not given when using umount? (Target is busy) #671

Open
bdh1993 opened this issue Mar 2, 2023 · 4 comments

Comments

@bdh1993
Copy link

bdh1993 commented Mar 2, 2023

If you look at the unmount() function in the "script > common" path, no option is applied.
Therefore, a lot of target is busy situations occur during the build.

You can solve this problem by attaching the "-lf" option when you do umount.

It worked in the local build. (I don't know if it's build from Docker.)

There was no problem when using the generated image.
Is there any other problem I don't know?

@XECDesign
Copy link
Member

Because using -l doesn't actually unmount it. It removes the mount entry, but as long as the files remain open, it's still busy and the same as being mounted in the background. It's only when the last reference to all open files is dropped that the umount actually happens. I may be wrong, but that's my understanding, and without having evidence that it's 100% safe, I don't want to risk it.

It would be better to understand why umount doesn't work int he first place. I haven't seen that problem in a while, so I assume it was an issue that has been resolved in an upstream package somewhere.

@bdh1993
Copy link
Author

bdh1993 commented Mar 3, 2023

Thank you.
I build it on my computer.
When building, I opened another window or searched the website.
In the process, you have to umount, but I think it's because there's a row hanging in the other process.
Would this issue be more free if build from Docker?

@XECDesign
Copy link
Member

When building, I opened another window or searched the website.
In the process, you have to umount, but I think it's because there's a row hanging in the other process.

Sorry, I don't quite get what you mean there.

I build it on my computer.

Out of curiosity, what distro are you running?

Would this issue be more free if build from Docker?

I don't know, I don't use docker for my own builds.

@bdh1993
Copy link
Author

bdh1993 commented Mar 6, 2023

Thank you.


I didn't just use the computer for build.

I was doing other things when the Raspberry Pi build script was running.
For example, using package installation commands etc.

Another process meant this.

I guessed that umount did not work because another operation was in progress.


I build the Raspberry Pi arm64 version from the Linux mint distribution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants