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 107281 - LTC4967-mkinitrd build bad ramdisk if fstab has acl set
LTC4967-mkinitrd build bad ramdisk if fstab has acl set
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: mkinitrd (Show other bugs)
s390 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-10-16 10:44 EDT by Duane Beyer
Modified: 2007-11-30 17:06 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-10-16 17:34:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Duane Beyer 2003-10-16 10:44:55 EDT
The following has be reported by IBM LTC:  
mkinitrd build bad ramdisk if fstab has acl set
Hardware Environment:z/900

Software Environment:RHEL-3 RC1

Steps to Reproduce:
1.add acl to fstab for root filesystem.
  cat /etc/fstab
    LABEL=/                 /                       ext3    acl,rw          1 1
    LABEL=/boot             /boot                   ext3    defaults        1 2
    none                    /dev/pts                devpts  gid=5,mode=620  0 0
    none                    /proc                   proc    defaults        0 0
    /dev/dasdc1             swap                    swap    defaults        0 0

2. Reboot system
3. run mkinitrd - update zipl.conf to point to new ramdisk. run zipl.
4. IPL System - get error mount the filesystem with the acl (see actual results)

5. update zipl.conf and point to the original ramdisk. run zipl.  
    IPL System - everything is fine.

6. remove acl,rw from fstab and rerun mkinitrd, update zipl.conf to point to 
the new ramdisk,  run zipl.
    IPL system,  everything is fine. (proof it is the acl in fstab)
Actual Results:System unable to mount the filesystem that had acl set on.

Checking root filesystem                                       
/dev/dasdb1 is mounted.  e2fsck: Cannot continue, 
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/dasdb1            

Expected Results: The system IPL's without errors and changes are picked up.

Additional Information:
Comment 1 Jeremy Katz 2003-10-16 16:04:34 EDT
The options field for the root fs should be defaults,acl not acl,rw -- does that
work better?
Comment 2 Duane Beyer 2003-10-16 17:25:51 EDT
yes, much better.  Please close as user error.  

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