Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#21947 - [devtools] arch-build fails to unmount the chroot's /dev sometimes

Attached to Project: Arch Linux
Opened by Evangelos Foutras (foutrelis) - Wednesday, 01 December 2010, 08:02 GMT
Last edited by Pierre Schmitz (Pierre) - Thursday, 02 December 2010, 17:20 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Pierre Schmitz (Pierre)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After using extra-x86_64-build to build a package, the chroot's /dev remains mounted. If I then proceed to run `umount /var/tmp/archbuild/extra-x86_64/copy/dev', it will unmount it successfully.

Example of the error message I receive after the package has been built:

umount: /var/tmp/archbuild/extra-x86_64/copy/dev: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))


Additional info:
* package version(s): devtools 0.9.13-1


Steps to reproduce:

Build a package using devtools (e.g.: extra-x86_64-build) and notice how sometimes the chroot's /dev doesn't get unmounted.
This task depends upon

Closed by  Pierre Schmitz (Pierre)
Thursday, 02 December 2010, 17:20 GMT
Reason for closing:  Fixed
Comment by Pierre Schmitz (Pierre) - Thursday, 02 December 2010, 15:57 GMT
Although I never saw such problems myself binding /dev from the host into a chroot is a bad idea anyway. Please try devtools-0.9.14-1 (in testing) and let me know if that works for you. It uses its own minimal /dev.
Comment by Evangelos Foutras (foutrelis) - Thursday, 02 December 2010, 17:08 GMT
I tried again with devtools 0.9.13 and got the same error. I then upgraded to 0.9.14 and the issue is now gone. Everything is working great, AFAICS.

Thanks for the quick resolution, Pierre. :)

Loading...