From: Eric Sandeen <sandeen@redhat.com>
To: darxus@chaosreigns.com
Cc: linux-ext4@vger.kernel.org, Tim Landscheidt <tim@tim-landscheidt.de>
Subject: Re: Weird filesystem corruption from wayland / radeon / chromium
Date: Thu, 15 Nov 2012 17:38:23 -0600 [thread overview]
Message-ID: <50A57CEF.30404@redhat.com> (raw)
In-Reply-To: <50A56635.20408@redhat.com>
On 11/15/12 4:01 PM, Eric Sandeen wrote:
> On 9/3/12 5:02 PM, 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)
>>
>> Same search_left... argument? Same inode?
>>
>> $ sudo find . -inum 21374007 -print
>> ./home/darxus/.cache/chromium/Default/Cache/data_3
>
> If you are still running into this, could you also do:
>
> debugfs -R "dump_extents <21374007>" /dev/sda1
>
> and send me and/or the list the result of that?
Oh, and a question for both of you guys - have you used e4defrag on this filesystem (or this file?)
-Eric
prev parent reply other threads:[~2012-11-15 23:38 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
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 [this message]
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=50A57CEF.30404@redhat.com \
--to=sandeen@redhat.com \
--cc=darxus@chaosreigns.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tim@tim-landscheidt.de \
/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 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.