xfs
[Top] [All Lists]

xfs_repair 3.2.0 cannot (?) fix fs

To: xfs@xxxxxxxxxxx
Subject: xfs_repair 3.2.0 cannot (?) fix fs
From: Arkadiusz MiÅkiewicz <arekm@xxxxxxxx>
Date: Sat, 28 Jun 2014 01:41:54 +0200
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=maven.pl; s=maven; h=from:to:subject:date:user-agent:mime-version:content-type :content-transfer-encoding:message-id; bh=e17ZVYoG3tw5LxnQou8ZxWiveEJGsE+5d0miEVcENYM=; b=OclAgTIk3I8hni9qHRh6B/i0573gyATLLp/p+mVql394jeL47LCG9lMgOEa5yesTks 3v6hPwUkBJyiU3l73wOV6nH/Y/R3zm3a7a81iMOrXaCtYtdz/OrEV7iils3LS+zVX+iV P1018MfA0OH5QM52vvYcnyXDK7+vGp/vMX7dA=
User-agent: KMail/1.13.7 (Linux/3.16.0-rc2-00211-gd7933ab; KDE/4.13.2; x86_64; ; )
Hello.

I have a fs (metadump of it
http://ixion.pld-linux.org/~arekm/p2/x1/web2-home.metadump.gz)
that xfs_repair 3.2.0 is unable to fix properly.

Running xfs_repair few times shows the same errors repeating:
http://ixion.pld-linux.org/~arekm/p2/x1/repair2.txt
http://ixion.pld-linux.org/~arekm/p2/x1/repair3.txt
http://ixion.pld-linux.org/~arekm/p2/x1/repair4.txt
http://ixion.pld-linux.org/~arekm/p2/x1/repair5.txt

(repair1.txt also exists - it was initial, very big/long repair)

Note that fs mounts fine (and was mounting fine before and after repair) but 
xfs_repair indicates that not everything got fixed.


Unfortunately there looks to be a problem with metadump image. xfs_repair is 
able to finish fixing on a restored image but is not able (see repairX.txt) 
above on real devices. Huh?

Examples of problems repeating each time xfs_repair is run:

1)
reset bad sb for ag 5
non-null group quota inode field in superblock 7

2) 
correcting nblocks for inode 965195858, was 19 - counted 20
correcting nextents for inode 965195858, was 16 - counted 17

3) clearing some entries; moving to lost+found (the same files)

4) 
Phase 7 - verify and correct link counts...
Invalid inode number 0xfeffffffffffffff
xfs_dir_ino_validate: XFS_ERROR_REPORT
Metadata corruption detected at block 0x11fbb698/0x1000
libxfs_writebufr: write verifer failed on bno 0x11fbb698/0x1000
Invalid inode number 0xfeffffffffffffff
xfs_dir_ino_validate: XFS_ERROR_REPORT
Metadata corruption detected at block 0x11fbb698/0x1000
libxfs_writebufr: write verifer failed on bno 0x11fbb698/0x1000
done

5)Metadata CRC error detected at block 0x0/0x200
but it is not CRC enabled fs

-- 
Arkadiusz MiÅkiewicz, arekm / maven.pl

<Prev in Thread] Current Thread [Next in Thread>