From: Luciano ES <lucmove@gmail.com>
To: XFS mailing list <linux-xfs@vger.kernel.org>
Subject: Re: XFS file system corruption, refuses to mount
Date: Sat, 3 Aug 2019 05:05:17 -0300 [thread overview]
Message-ID: <20190803050517.55b15f57@lud1.home> (raw)
In-Reply-To: <20190803011106.GJ7138@magnolia>
On Fri, 2 Aug 2019 18:11:06 -0700, Darrick J. Wong wrote:
> > Is there something I can do to recover the data?
>
> Try xfs_repair -n to see what it would do if you ran repair?
I tried it. It took a very long time.
Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!
attempting to find secondary superblock...
...................................... (a million dots)
Sorry, could not find valid secondary superblock
Exiting now.
I tested the file system (unlocked) with the fsck, lsblk, blkid and
file commands, all of which confirm that it is an XFS file system.
It just won't mount. Is there any recovery procedure?
--
Luciano ES
>>
next prev parent reply other threads:[~2019-08-03 8:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 20:32 I got file system corruption with XFS Luciano ES
2018-12-11 20:57 ` Eric Sandeen
2018-12-11 22:54 ` Luciano ES
2018-12-12 1:01 ` Eric Sandeen
2018-12-11 21:27 ` Dave Chinner
2019-03-31 22:49 ` File system corruption in two hard disks Dave Chinner
2019-04-01 21:13 ` Luciano ES
2019-04-01 21:32 ` Dave Chinner
2019-04-02 16:23 ` Luciano ES
2019-04-02 16:42 ` Eric Sandeen
2019-04-02 18:54 ` Chris Murphy
2019-04-02 21:37 ` Dave Chinner
2019-08-03 0:53 ` XFS file system corruption, refuses to mount Luciano ES
2019-08-03 1:11 ` Darrick J. Wong
2019-08-03 1:53 ` Luciano ES
2019-08-03 5:35 ` Dave Chinner
2019-08-03 8:05 ` Luciano ES [this message]
2019-08-15 20:32 ` XFS file system " Luciano ES
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=20190803050517.55b15f57@lud1.home \
--to=lucmove@gmail.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;
as well as URLs for NNTP newsgroup(s).