> On Wed, Dec 24, 2008 at 2:09 PM, <[email protected]> wrote: > >> Are the filesystems incompatible? > > they are not incompatible, verified by one of RedHat's ext engineers > > Maybe I asked the wrong question. If the e2fsck program that comes > with rhel3 is is not [fully] compatible with the rhel5 filesystem, > that is a problem though, even though the filesystem itself can be > mounted and used. Again, hopefully a reboot won't be needed anytime > soon! > > > While technically it should be fine, you can remove the ext_attr in this > > manner: > > I agree that your tests suggest that ext_attr isn't the problem. > Maybe the problem is among these other 'filesystem features' that the > rhel5-created filesystem has, that aren't among features listed for > the rhel3-created filesystems: resize_inode, dir_index, large_file; > plus these default mount options (also as indicated by dumpe2fs): > user_xattr, acl. I'm not sure which of these prevents rhel3 from > being able to fsck the device, and currently it's in use, so I can't > experiment with changing anything.
maybe I misread.. For some reason I thought the error was when you tried to mount, not when you tried to fsck the file system. I just played with the fsck and to get rhel3 to fsck the rhel5 originating filesystem I had to ermove the "resize_inode" feature. I did this like this: debugfs -w /dev/path -R "features ^resize_inode" then fsck ran fine, but not before. -greg _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
