DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=bmQ6gSAC6KM76BnSYYUOsJOJMeDIPKNBnwMlKfWRj8CJ0kPiqcCNUVEGgJ3HhqAcfX
         /72XlnWyAZ64GtP1R8NrzPVBdO0DvVpi4OrH6CCOy7Fo5YJrxJY16pNkEEZUBL0xIRfs
         tLafrXZQi0062A1qtGpy4vhbjYDgP+Bbq95PA=
MIME-Version: 1.0
Date: Mon, 7 Jun 2010 14:45:38 -0600
Message-ID: <AANLkTinQatQEYahpkN3bT-S5C41HqRoH--gTrvIbGs_c@mail.gmail.com>
Subject: EXT3 File System Corruption 2.6.34
From: Jeffrey Merkey <jeffmerkey@gmail.com>
To: linux-kernel@vger.kernel.org
Content-Type: text/plain; charset=ISO-8859-1
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1152
Lines: 23

Still seeing file system corruption after journal recovery in EXT3.
It's easy to reproduce, though the symptoms vary.  One way is to
rebuild a program and while the program is being compiled just shut
off power to the system by pulling the plug.  I am seeing the
/root/.viminfo file trashed after recovery if Vim was active during
poweroff.  I am also seeing object modules getting built which the LD
linker claims are "invalid" following a recovery event.  I suspect a
bug in the buffer cache since deleting the file still causes the old
data to be returned from buffer cache even when the sectors are
overwritten, but both are interrelated.  Seems in some way related to
EXT3 recovery which results in the buffer cache returning old sectors
and junk.

Not hard to reproduce, but the symptoms are always a little different
but the /root/.viminfo file getting nuked seems a common affect of
this bug.

Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/