Summary: | halt.sh fails to unmount manually set up dmcrypt mounts and loopbacks | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Peter Hyman <pete4abw> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Peter Hyman
2006-01-07 08:03:58 UTC
you're probably going to have to track this down yourself ... look in the halt.sh script, there is already logic in there for unmounting dm-crypt loop devices regardless of how they were actually mounted remaining=$(awk '!/^#/ && $1 ~ /^\/dev\/loop/ && $2 != "/" {print $2}' proc/mounts | \... When dmcrypt is used, the device in /proc/mounts is /dev/mapper, not /dev/loop. This is why no loopbacks get removed. Check out this fragment: peter@mars ~ $ grep "^\/dev\/loop\|^\/dev\/mapper" /proc/mounts /dev/mapper/stuff /home/peter/mnt/stuff ext2 rw,nogrpid 0 0 As opposed to: peter@mars ~ $ grep "^\/dev\/loop" /proc/mounts peter@mars ~ $ I believe the addition of the simple conditional for /dev/mapper in halt.sh will fix the problem. Will report. Well, that was fun. Unfortunately, while the loopback test _DID_ find the /dev/mapper device and removed it, the dmcrypt addon never ran since I don't have a /etc/cryptfs file set up. So, shutdown still hangs because halt.sh doesn't disconnect the dmcrypt device. That's why /home/peter never can unmount. I want to keep these files completely in userspace, so I suppose I will have to remember to unmount it by hand, or add it to local.stop or suffer with the error. Marking cantfix unless you can think of a better way. I'll play around with fuse too. This really is a user-level problem, not system. |