From: Eric Sandeen <sandeen@redhat.com>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH] xfs_repair: validate & fix inode CRCs
Date: Tue, 16 Sep 2014 16:30:41 -0500 [thread overview]
Message-ID: <5418AC01.30006@redhat.com> (raw)
xfs_repair doesn't ever check an inode's CRC, so it never repairs
them. If the root inode or realtime inodes have bad crcs, the
fs won't even mount and can't be fixed (without using xfs_db).
It's fairly straightforward to just test the inode CRC before
we do any other checking or modification of the inode, once we
get past the "verify only" phase of process_dinode_int();
just mark it dirty if it's wrong and needs to be re-written.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
forgive the gratuitous big honkin' comment line, but
process_dinode_int is so long, I thought the visual delimiter was
useful. ;)
diff --git a/repair/dinode.c b/repair/dinode.c
index 8891e84..27c0da6 100644
--- a/repair/dinode.c
+++ b/repair/dinode.c
@@ -2524,6 +2524,30 @@ _("bad (negative) size %" PRId64 " on inode %" PRIu64 "\n"),
if (verify_mode)
return retval;
+ /* =========== END OF VERIFY MODE =================== */
+
+ /*
+ * We'd really like to know if the CRC is bad before we
+ * go fixing anything; that way we have some hint about
+ * bit-rot vs bugs. Also, any changes will invalidate the
+ * existing CRC, so this is the only valid point to test it.
+ *
+ * Of course if we make any modifications after this, the
+ * inode gets rewritten, and CRC is updated automagically.
+ */
+ if (xfs_sb_version_hascrc(&mp->m_sb)) {
+ ASSERT(!verify_mode);
+ if(!xfs_verify_cksum((char *)dino, mp->m_sb.sb_inodesize,
+ XFS_DINODE_CRC_OFF)) {
+ do_warn(_("bad CRC for inode %" PRIu64), lino);
+ if (!no_modify) {
+ do_warn(_(", will rewrite\n"));
+ *dirty = 1;
+ } else
+ do_warn(_(", would rewrite\n"));
+ }
+ }
+
/*
* clear the next unlinked field if necessary on a good
* inode only during phase 4 -- when checking for inodes
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-09-16 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 21:30 Eric Sandeen [this message]
2014-09-22 13:18 ` [PATCH] xfs_repair: validate & fix inode CRCs Brian Foster
2014-09-22 14:45 ` Eric Sandeen
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=5418AC01.30006@redhat.com \
--to=sandeen@redhat.com \
--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