From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Luciano ES <lucmove@gmail.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: XFS file system corruption, refuses to mount
Date: Fri, 2 Aug 2019 18:11:06 -0700 [thread overview]
Message-ID: <20190803011106.GJ7138@magnolia> (raw)
In-Reply-To: <20181211183203.7fdbca0f@lud1.home>
On Fri, Aug 02, 2019 at 09:53:56PM -0300, Luciano ES wrote:
> I've had this internal disk running for a long time. I had to
> disconnect it from the SATA and power plugs for two days.
> Now it won't mount.
>
> mount: wrong fs type, bad option, bad superblock on /dev/mapper/cab3,
> missing codepage or helper program, or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so.
>
> I get this in dmesg:
>
> [ 30.301450] XFS (dm-1): Mounting V5 Filesystem
> [ 30.426206] XFS (dm-1): Corruption warning: Metadata has LSN
> (16:367696) ahead of current LSN (16:367520). Please unmount and run
> xfs_repair (>= v4.3) to resolve.
Hm, I think this means the superblock LSN is behind the log LSN, which
could mean that... software is buggy? The disk didn't flush its cache
before it was unplugged? Something else?
What kernel & xfsprogs?
And how did you disconnect it from the power plugs?
> [ 30.426209] XFS (dm-1): log mount/recovery failed: error -22
> [ 30.426310] XFS (dm-1): log mount failed
>
> Note that the entire disk is encrypted with cryptsetup/LUKS,
> which is working fine. Wrong passwords fail. The right password
> opens it. But then it refuses to mount.
>
> This has been happening a lot to me with XFS file systems.
> Why is this happening?
>
> Is there something I can do to recover the data?
Try xfs_repair -n to see what it would do if you ran repair?
--D
> --
> Luciano ES
> >>
next prev parent reply other threads:[~2019-08-03 1:13 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 [this message]
2019-08-03 1:53 ` Luciano ES
2019-08-03 5:35 ` Dave Chinner
2019-08-03 8:05 ` Luciano ES
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=20190803011106.GJ7138@magnolia \
--to=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=lucmove@gmail.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;
as well as URLs for NNTP newsgroup(s).