We're starting to get some testing of ext4 on RHEL5, and we may get it to a tech
preview status by RHEL5.3 - to support this, a few system utilities could use
updates for ext4.
dump/restore won't open an ext4 filesystem. Need to investigate what all it'll
take to properly support ext4 in dump/restore.
[root@inode ~]# dump -f /mnt/foo/mydump /mnt/test
DUMP: Date of this level dump: Mon Apr 28 17:11:13 2008
DUMP: Dumping /dev/sda8 (/mnt/test) to /mnt/foo/mydump
DUMP: Unsupported feature(s) 0x40 in filesystem
/dev/sda8: Filesystem has unsupported feature(s) while opening filesystem
DUMP: The ENTIRE dump is aborted.
I haven't yet looked at dump to see how much fs-knowledge it needs for the
This is big problem. Dump needs detailed FS knowledge, it operates directly with
inodes. I recommend follow standard scenario - Fedora->(upstream)->RHEL. I'm
affraid I cannot make it to 5.3. Btw ext3 support in dump is still marked as
experimental and upstream doesn't have time for such development.
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
*** Bug 504537 has been marked as a duplicate of this bug. ***
Support for ext4 was submitted in this message to the devel list.
A new release happened last Thursday (2008-06-18), here's the announcement.
A big update, 0.4b42, was released this week that includes ext4 support. Please test it and let upstream know. Here's the release announcement:
I see that the new release has hit Rawhide:
After discussion ext4 support won't be available in RHEL5.
Ext4 support requires improved e2fsprogs-libs with ext4 support. From e2fsprogs-libs maintainer perspective it will be so difficult and invasive to extend the library thus dump with ext4 will be available in RHEL6.
*** Bug 733318 has been marked as a duplicate of this bug. ***