Just changing the CC to opensuse-kernel. I had factory in CC
mistakenly when I replied to Jan.
On Fri, Apr 8, 2011 at 2:50 PM, Jan Kara <jack(a)suse.cz> wrote:
> On Fri 08-04-11 14:37:41, Greg Freemyer wrote:
>> On Thu, Apr 7, 2011 at 6:53 PM, Jan Kara <jack(a)suse.cz> wrote:
>> > On Thu 07-04-11 16:50:16, Greg Freemyer wrote:
>> > > On Thu, Apr 7, 2011 at 2:57 PM, Jan Kara <jack(a)suse.cz> wrote:
>> > > > 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
>> > > > --
>> > > > Jan Kara <jack(a)suse.cz>
>> > > > SUSE Labs, CR
>> > > >
>> > >
>> > > 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.
>> > I would not expect it to eat a filesystem actually. Kernel crash is
>> > possible but fs corruption (even more a one which is hard to fix) rather
>> > unlikely.
>> >
>> >
>> If filesystem corruption is unlikely and hard to fix corruption is rather
>> unlikely, then I would take the advice of the EXT3 driver maintainer.
>> (ie. Jan himself).
Thanks ;). Actually, my confidence is partly backed by the fact that
Google cloud uses ext4 in nojournal mode (i.e. as an ext2 replacement) for
about an year now and they are happy. That is a *lot* of stress testing.
They don't use completely the same code path as our users (in Google they
use extents, our users would stay with indirect blocks unless they'd
manually migrate) but a lot of it is the same.
Honza
--
Jan Kara <jack(a)suse.cz>
SUSE Labs, CR
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org