From: Avi Kivity <avi@scylladb.com>
To: linux-xfs@vger.kernel.org
Subject: filesystem dead, xfs_repair won't help
Date: Mon, 10 Apr 2017 12:23:51 +0300 [thread overview]
Message-ID: <CAF950WLvp7SWnDHU_AY+j3CYtCDWYLdN=AkNZgNB2yU3sVxsJQ@mail.gmail.com> (raw)
Today my kernel complained that in memory metadata is corrupt and
asked that I run xfs_repair. But xfs_repair doesn't like the
superblock and isn't able to find a secondary superblock.
Latest Fedora 25 kernel, new Intel NVMe drive (worked for a few weeks
without issue).
Anything I can do to recover the data?
next reply other threads:[~2017-04-10 9:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 9:23 Avi Kivity [this message]
2017-04-10 9:42 ` filesystem dead, xfs_repair won't help 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
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='CAF950WLvp7SWnDHU_AY+j3CYtCDWYLdN=AkNZgNB2yU3sVxsJQ@mail.gmail.com' \
--to=avi@scylladb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.