From: Theodore Ts'o <tytso@mit.edu>
To: darxus@chaosreigns.com
Cc: linux-ext4@vger.kernel.org
Subject: Re: Weird filesystem corruption from wayland / radeon / chromium
Date: Mon, 3 Sep 2012 23:29:19 -0400 [thread overview]
Message-ID: <20120904032919.GJ5066@thunk.org> (raw)
In-Reply-To: <20120903220213.GE19158@chaosreigns.com>
On Mon, Sep 03, 2012 at 06:02:13PM -0400, darxus@chaosreigns.com wrote:
> [732715.730069] EXT4-fs error (device sda1): ext4_ext_search_left:1275: inode #21374007: comm flush-8:0: ix (10742) != EXT_FIRST_INDEX (0)
> [ 496.347230] EXT4-fs error (device sda1): ext4_ext_search_left:1275: inode #21374007: comm flush-8:0:ix (10742) != EXT_FIRST_INDEX (0)
>
> What is the significance of this file? What does the error mean?
The error means that the metadata associated with one of Chromium's
cache files had gotten corrected. You say you saw this exact same
error separated in time by three months. Between those three months,
was the file system corruption fixed by an e2fsck run?
If not, the fact that you are getting this message twice isn't
surprising. The e2fsck program *should* have been run at each reboot,
but this error may have required manual intervention to fix up.
If you did run e2fsck, and the file system corruptions was fixed
between the two times that you saw the EXT4-fs error message, then
that is very interesting. I would discount scribbling over kernel
memory, since it would be pretty unusual that the exact same inode and
the exact same block had gotten corrupted in exactly the same way. It
could be a bug in the graphics driver, perhaps triggered by the way
Wayland is using said graphics driver.
That also seems fairly hard to credit, so I'm going to hope you didn't
actually run e2fsck to fix the file system corruption....
- Ted
next prev parent reply other threads:[~2012-09-04 3:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 22:02 Weird filesystem corruption from wayland / radeon / chromium darxus
2012-09-04 3:29 ` Theodore Ts'o [this message]
2012-09-04 7:19 ` darxus
2012-09-05 2:48 ` darxus
2012-09-05 3:38 ` darxus
2012-11-02 15:50 ` Tim Landscheidt
2012-11-02 17:24 ` Eric Sandeen
2012-11-02 18:55 ` Tim Landscheidt
2012-11-13 18:28 ` Eric Sandeen
2012-11-13 22:13 ` Eric Sandeen
2012-11-12 22:00 ` Eric Sandeen
2012-11-15 22:01 ` Eric Sandeen
2012-11-15 23:38 ` Eric Sandeen
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=20120904032919.GJ5066@thunk.org \
--to=tytso@mit.edu \
--cc=darxus@chaosreigns.com \
--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).