linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Flater <dflater@nist.gov>
To: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: fs corruption with 2.6.28-ext4-4
Date: Wed, 21 Jan 2009 15:36:03 -0500	[thread overview]
Message-ID: <49778733.4030307@nist.gov> (raw)

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.



                 reply	other threads:[~2009-01-21 20:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49778733.4030307@nist.gov \
    --to=dflater@nist.gov \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).