From: Emmanuel Florac <eflorac@intellique.com>
To: Avi Kivity <avi@scylladb.com>
Cc: Brian Foster <bfoster@redhat.com>, linux-xfs@vger.kernel.org
Subject: Re: filesystem dead, xfs_repair won't help
Date: Tue, 11 Apr 2017 13:30:33 +0200 [thread overview]
Message-ID: <20170411133033.65c89ee8@harpe.intellique.com> (raw)
In-Reply-To: <974df72a-04fe-fba4-4b48-89426b8783e0@scylladb.com>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
Le Tue, 11 Apr 2017 10:46:07 +0300
Avi Kivity <avi@scylladb.com> écrivait:
> $ sudo xfs_repair /dev/nvme0n1
> Phase 1 - find and verify superblock...
> couldn't verify primary superblock - not enough secondary superblocks
> with matching geometry !!!
Which version of xfs_repair is this?
Try to export the FS structure with xfs_metadump, something like
xfs_metadump /dev/nvme0n1 /some/file.dmp
And check the errors it reports, they may be informative.
In the case where metadump works out fine, you should then try to have a
look at the FS structure using the dump (to avoid wrecking it more that
it already is):
xfs_db -c "sb 0" /some/file.dmp
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
[-- Attachment #2: Signature digitale OpenPGP --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-04-11 11:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 9:23 filesystem dead, xfs_repair won't help Avi Kivity
2017-04-10 9:42 ` Avi Kivity
2017-04-10 15:35 ` Brian Foster
2017-04-11 7:46 ` Avi Kivity
2017-04-11 11:30 ` Emmanuel Florac [this message]
2017-04-11 11:40 ` Avi Kivity
2017-04-11 12:00 ` Emmanuel Florac
2017-04-11 12:03 ` Avi Kivity
2017-04-11 12:49 ` Emmanuel Florac
2017-04-11 13:07 ` Avi Kivity
2017-04-11 16:13 ` Emmanuel Florac
2017-04-11 16:44 ` Avi Kivity
2017-04-11 16:48 ` Eric Sandeen
2017-04-12 15:15 ` Christoph Hellwig
2017-04-12 15:34 ` Eric Sandeen
2017-04-12 15:45 ` Christoph Hellwig
2017-04-12 16:15 ` Avi Kivity
2017-04-12 16:20 ` Christoph Hellwig
2017-04-12 16:22 ` Eric Sandeen
2017-04-12 16:24 ` Avi Kivity
2017-04-12 16:22 ` Avi Kivity
2017-04-12 17:41 ` Christoph Hellwig
2017-04-10 9:43 ` allow mounting w/crc-checking disabled? (was Re: filesystem dead, xfs_repair won't help) L A Walsh
2017-04-10 16:01 ` Eric Sandeen
2017-04-10 18:05 ` L A Walsh
2017-04-11 12:57 ` Emmanuel Florac
2017-04-11 13:34 ` Eric Sandeen
2017-04-11 16:18 ` Emmanuel Florac
2017-04-11 16:34 ` Eric Sandeen
2017-04-10 15:49 ` filesystem dead, xfs_repair won't help Eric Sandeen
2017-04-10 16:23 ` Christoph Hellwig
2017-04-11 7:48 ` Avi Kivity
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=20170411133033.65c89ee8@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=avi@scylladb.com \
--cc=bfoster@redhat.com \
--cc=linux-xfs@vger.kernel.org \
/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