Bug 177781 - mkinitrd init script leaves /loopfs mounted read-write
mkinitrd init script leaves /loopfs mounted read-write
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: mkinitrd (Show other bugs)
4
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Peter Jones
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-01-13 17:00 EST by Ed Swierk
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 5.0.20-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-03 18:07:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ed Swierk 2006-01-13 17:00:01 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051201 Fedora/1.5-1.1.fc4.nr Firefox/1.5

Description of problem:
I am booting Fedora from a root filesystem image file that is stored in an ext3 filesystem on /dev/hda1.  mkinitrd generates an init script that handles all the loopback magic just fine.

The only problem is that the init script leaves the filesystem containing the root image mounted read-write on /loopfs.  When I try to mount the same filesystem after the system finishes booting, fsck has to do a journal recovery because the filesystem is dirty.

/proc/mounts shows the filesystem still mounted as /loopfs.  However, when I try umount /dev/hda1, I get "not mounted".


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
Run mkinitrd with / configured as /dev/loop0, and the loopFs stored on an ext3 (or any writable) filesystem.  /etc/fstab looks like this:

/dev/loop0     /         ext3    defaults  1 1
# LOOP0: /dev/hda1 ext3 /boot/rootfs
/dev/hda1      /disk     ext3    defaults  1 1


Expected Results:  The init script should mount the loopfs read-only, since the only thing it needs to do is read the root filesystem image file.


Additional info:

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