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, 
aborting.                                                                   
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/dasdb1            
[FAILED]                                                       

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

Additional Information: