Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 591829 - disabling /dev/loop0 LOOP_CLR_FD failed: 16
disabling /dev/loop0 LOOP_CLR_FD failed: 16
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
rawhide
All Linux
low Severity medium
: ---
: ---
Assigned To: Brian Lane
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-13 05:57 EDT by Liam Li
Modified: 2010-05-18 12:00 EDT (History)
2 users (show)

See Also:
Fixed In Version: anaconda-14.6-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-18 12:00:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
disable loop (9.36 KB, image/png)
2010-05-13 05:57 EDT, Liam Li
no flags Details

  None (edit)
Description Liam Li 2010-05-13 05:57:26 EDT
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):
anaconda13.42

How reproducible:
always

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 11:26:53 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.