All of lore.kernel.org
 help / color / mirror / Atom feed
* fs corruption with 2.6.28-ext4-4
@ 2009-01-21 20:36 David Flater
  0 siblings, 0 replies; only message in thread
From: David Flater @ 2009-01-21 20:36 UTC (permalink / raw)
  To: linux-ext4

I am guessing that this doesn't belong in bugzilla since it's not a 
mainline kernel I'm talking about.  Sorry if this is still the wrong venue.

On two different computers, I experienced file system corruption after 
upgrading the kernel to 2.6.28-ext4-4 (meaning, mainline 2.6.28 kernel 
with the 2.6.28-ext4-4 patchset from 
http://www2.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/ applied).

On Computer #1, an ext4 file system would not mount on reboot.  fsck 
reported that hundreds (all?) of the group descriptors were corrupted.

On Computer #2, the ext2 file system on an external drive became 
corrupted with cross linked blocks.  The file system mounted but the 
kernel soon began reporting problems with it.

In both cases, the corruption seemed to occur at about the time that I 
created a large file (> 4 GiB) using the 2.6.28-ext4-4 kernel.  An older 
computer that I configured with the same kernel and an ext4 file system 
for testing, before the others were upgraded, still has no problems--but 
it has a smaller hard drive and no large files.

I am in the process of reverting to a stable configuration, but please 
accept this experience report for what it is worth.

Thank you,

-- 
David Flater, National Institute of Standards and Technology, U.S.A.



^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2009-01-21 20:36 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-21 20:36 fs corruption with 2.6.28-ext4-4 David Flater

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.