xfs_repair fails to repair, run under valgrind shows "Invalid read..." and XFS_CORRUPTION_ERROR

Cody P Schafer cody at linux.vnet.ibm.com
Tue Feb 11 14:18:32 CST 2014


On 02/11/2014 12:11 PM, Eric Sandeen wrote:
> On 2/11/14, 1:55 PM, Cody P Schafer wrote:
>> xfsprogs version: v3.2.0-alpha2-14-g6e79202
>>
>> uname: Linux hostname 3.11.10-301.fc20.ppc64 #1 SMP Tue Dec 10 00:35:15 MST 2013 ppc64 POWER8 (architected), altivec supported CHRP IBM,8286-42A GNU/Linux
>>
>> full log attached.
>
> Yikes, that's one destroyed filesystem.  What happened?
>

Well, initially? no idea. This is the second time that the repair 
failed, so the first one may not have been too kind to the system. The 
fs still mounts fine (or did before this particular failed repair), but 
has random file corruption (pieces of files get replaced with other 
junk). Most of the time without any XFS_CORRUPTION errors showing up in 
dmesg (though they did appear a few times in the past).



More information about the xfs mailing list