Red Hat Bugzilla – Bug 43919
losetup prevents shutdown from unmounting fs causing fsck next boot
Last modified: 2014-03-16 22:21:09 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT)
Description of problem:
When using a filesystem in a file I used the losetup command to associate
it with a loop device. When I shut my system down it was unable to unmount
the filesystem containing the file (in my case /).
Steps to Reproduce:
1. losetup /dev/loop0 filename
2. shutdown / powerdown / halt
Actual Results: /etc/rc.d/init.d/halt failed to unmount filesystem
containing the file that losetup was run on. Next boot requires fsck.
Expected Results: Clean shutdown.
Manually doing losetup -d /dev/loop0 before shutdown avoids the problem
but as /etc/rc.d/init.d/halt manages to unmount loopback filesystems I
think it should also remove the loopback device if needed as well. The
halt script does handle the following way of using the loopback device:
mount imagefile /mnt/point -t fstype -o loop=/dev/loop0
losetup /dev/loop0 imagefile
mount -t fstype /dev/loop0 /mnt/point
Will be fixed in initscripts-6.12-1.