From: Avi Kivity <avi@scylladb.com>
To: Emmanuel Florac <eflorac@intellique.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 15:03:12 +0300 [thread overview]
Message-ID: <9d2587d5-e1f1-e5bb-d276-bc6731b2fce8@scylladb.com> (raw)
In-Reply-To: <20170411140007.05af2bcd@harpe.intellique.com>
On 04/11/2017 03:00 PM, Emmanuel Florac wrote:
> Le Tue, 11 Apr 2017 14:40:15 +0300
> Avi Kivity <avi@scylladb.com> écrivait:
>
>> $ sudo xfs_db -c "sb 0" /tmp/fs
>> xfs_db: /tmp/fs is not a valid XFS filesystem (unexpected SB magic
>> number 0x5846534d)
>> Use -F to force a read attempt.
>> $ sudo xfs_db -F -c "sb 0" /tmp/fs
>> xfs_db: /tmp/fs is not a valid XFS filesystem (unexpected SB magic
>> number 0x5846534d)
>> xfs_db: V1 inodes unsupported. Please try an older xfsprogs.
> Oops, I forgot one important part, sorry, you must restore the
> meta_dump to a file first:
>
> xfs_mdrestore /tmp/fs /tmp/fsimage
>
> then run xfs_db on the /tmp/fsimage:
>
> xfs_db -c 'sb 0' -c 'p' /tmp/fsimage
>
magicnum = 0x58465342
blocksize = 4096
dblocks = 125026902
rblocks = 0
rextents = 0
uuid = 50b25ad8-3eb9-4273-b7f2-d0a435b3a08f
logstart = 67108869
rootino = 96
rbmino = 97
rsumino = 98
rextsize = 1
agblocks = 31256726
agcount = 4
rbmblocks = 0
logblocks = 61048
versionnum = 0xb4b5
sectsize = 512
inodesize = 512
inopblock = 8
fname = "\000\000\000\000\000\000\000\000\000\000\000\000"
blocklog = 12
sectlog = 9
inodelog = 9
inopblog = 3
agblklog = 25
rextslog = 0
inprogress = 0
imax_pct = 25
icount = 1959744
ifree = 89
fdblocks = 91586587
frextents = 0
uquotino = null
gquotino = null
qflags = 0
flags = 0
shared_vn = 0
inoalignmt = 4
unit = 0
width = 0
dirblklog = 0
logsectlog = 0
logsectsize = 0
logsunit = 1
features2 = 0x18a
bad_features2 = 0x18a
features_compat = 0
features_ro_compat = 0x1
features_incompat = 0x1
features_log_incompat = 0
crc = 0x3ebf41de (correct)
spino_align = 0
pquotino = null
lsn = 0x70002828b
meta_uuid = 00000000-0000-0000-0000-000000000000
next prev parent reply other threads:[~2017-04-11 12:03 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
2017-04-11 11:40 ` Avi Kivity
2017-04-11 12:00 ` Emmanuel Florac
2017-04-11 12:03 ` Avi Kivity [this message]
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=9d2587d5-e1f1-e5bb-d276-bc6731b2fce8@scylladb.com \
--to=avi@scylladb.com \
--cc=bfoster@redhat.com \
--cc=eflorac@intellique.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