<resend in plain text> On Thu, Apr 7, 2011 at 2:57 PM, Jan Kara <jack@suse.cz> wrote:
Hello,
we are figuring out upstream how to eventually get rid of maintaing three code bases of ext2, ext3, and ext4 in parallel. These days ext4 kernel driver is able to handle both ext2 and ext3 filesystems in a backward compatible manner - i.e., you can mount, access, modify the filesystem with ext4 driver and then still be able to use it with the old ext2 driver. So I'd think that we could try changing config of our kernel in Factory so that ext4 driver is used for ext2 filesystem and see whether something breaks or not.
Do people have any opinion on this?
Honza
I think it is a good idea. It is something easily reverted late in the release cycle, so there is not that much danger from a release cycle perspective. Conceivably it could eat a filesystem or two, but I have often heard it said that factory can do that, especially very early in the cycle like we are right now. fyi: on a smaller scale I will be asking the same thing about a patch to mkfs.ext4 that has been in use for CTERA production for a year or so. It has been tested heavily in that environment, but not in a broad set of environments. Thoughts about doing that in the short term would also be welcome. fyi: Jan, I'm just proposing to package Amir Goldstein's patch for e2fsprogs. My hope is to get the full next4 kernel module into factory with experimental status once factory moves to 2.6.39. Greg -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org