From: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
To: xfs@oss.sgi.com
Subject: xfs_repair 3.2.0 cannot (?) fix fs
Date: Sat, 28 Jun 2014 01:41:54 +0200 [thread overview]
Message-ID: <201406280141.54350.arekm@maven.pl> (raw)
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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-06-27 23:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 23:41 Arkadiusz Miśkiewicz [this message]
2014-06-28 21:52 ` xfs_repair 3.2.0 cannot (?) fix fs Arkadiusz Miśkiewicz
2014-06-28 22:01 ` Arkadiusz Miśkiewicz
2014-06-30 3:18 ` Dave Chinner
2014-06-30 3:44 ` Dave Chinner
2014-06-30 5:36 ` Arkadiusz Miśkiewicz
2014-06-30 11:12 ` Dave Chinner
2014-06-30 11:53 ` Arkadiusz Miśkiewicz
2014-06-30 12:06 ` Dave Chinner
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=201406280141.54350.arekm@maven.pl \
--to=arekm@maven.pl \
--cc=xfs@oss.sgi.com \
/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