Re: Weird filesystem corruption from wayland / radeon / chromium

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/15/12 4:01 PM, Eric Sandeen wrote:
> On 9/3/12 5:02 PM, darxus@xxxxxxxxxxxxxxx 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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux