Bug 591829

Summary: disabling /dev/loop0 LOOP_CLR_FD failed: 16
Product: [Fedora] Fedora Reporter: Liam Li <lili>
Component: anacondaAssignee: Brian Lane <bcl>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: anaconda-14.6-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-18 16:00:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
disable loop none

Description Liam Li 2010-05-13 09:57:26 UTC
Created attachment 413703 [details]
disable loop

Description of problem:

After install f13-final-rc3, reboot, echoes "disabling /dev/loop0 LOOP_CLR_FD failed: 16". This only appears on the reboot after install finished,does not appear during normal system reboot 
Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.install f13-final-rc3
2.after installation completed, press reboot
3.will echo "disabling /dev/loop0 LOOP_CLR_FD failed: 16"
4. but log in installed system, reboot system, this will not happen
Actual results:

Expected results:
After install successfully completed, should not give failed information, the screen shot, please see attachment.

Additional info:

Comment 1 Chris Lumens 2010-05-14 15:26:53 UTC
Since we're doing lazy unmounts now (MNT_DETACH in loader/undomounts.c:undoMount), we cannot guarantee that /mnt/runtime will be unmounted when we call undoLoop on /dev/loop0.  That's the device backing that mount point.  However, we should still try because we may want to tear down other loopback devices as well.  Therefore, I think the "fix" here is to just not display an error message.