From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/4] repair: fixes for 3.2
Date: Tue, 1 Jul 2014 22:54:52 +1000 [thread overview]
Message-ID: <1404219296-29302-1-git-send-email-david@fromorbit.com> (raw)
Hi Arkadiusz,
These are the fixes I have so far from working through the metadumps
you supplied me with. The unobfuscated metadump repairs cleanly with
these patches, but the obfuscated one still has a directory rebuild
issue that I haven't got to the bottom of yet. That results in
an error in phase 6 like:
Metadata corruption detected at block 0x2af84770/0x1000
name create failed in ino 2306912354 (117), filesystem may be out of space
It appears that a read verifier is on a recently created
directory leaf block and that is failing. I'm not yet sure why the
leaf block is corrupt, nor why the verifier is even being run on it
seeing as it was only allocated and initialised during the directory
rebuild. That directory rebuil dfailure is the reason for all the
disconected inode that end up in lost+found, and I think it's the
only remaining issue that I need to solve.
Can you test the patches on you machine and see if you get the same
results?
Cheers,
Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-07-01 12:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 12:54 Dave Chinner [this message]
2014-07-01 12:54 ` [PATCH 1/4] repair: handle directory block corruption in phase 6 Dave Chinner
2014-07-01 12:54 ` [PATCH 2/4] libxfs: buffers aren't stale once written Dave Chinner
2014-07-01 12:54 ` [PATCH 3/4] repair: fix quota inode handling in secondary superblocks Dave Chinner
2014-07-01 12:54 ` [PATCH 4/4] repair: get rid of BADFSINO Dave Chinner
2014-07-01 13:43 ` Arkadiusz Miśkiewicz
2014-07-01 13:40 ` [PATCH 0/4] repair: fixes for 3.2 Arkadiusz Miśkiewicz
2014-07-01 20:03 ` 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=1404219296-29302-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.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