Bug 43919

Summary: losetup prevents shutdown from unmounting fs causing fsck next boot
Product: [Retired] Red Hat Linux Reporter: David Wilson <david>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: low Docs Contact:
Priority: medium    
Version: 7.1CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-06-08 02:57:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description David Wilson 2001-06-08 02:57:55 UTC
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 /).

How reproducible:

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.

Additional info:

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

but not

losetup /dev/loop0 imagefile
mount -t fstype /dev/loop0 /mnt/point

Comment 1 Bill Nottingham 2001-08-07 06:57:46 UTC
Will be fixed in initscripts-6.12-1.