linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>, Jorge Garcia <jgarcia@soe.ucsc.edu>
Cc: linux-xfs@vger.kernel.org
Subject: Re: XFS corruption after power surge/outage
Date: Mon, 12 Feb 2024 16:39:12 -0600	[thread overview]
Message-ID: <fd31d2df-0378-4337-8841-7d811a8de1d0@sandeen.net> (raw)
In-Reply-To: <ZcqITqNBz6pmgiHJ@dread.disaster.area>

On 2/12/24 3:06 PM, Dave Chinner wrote:
> That has the XFS_SB_FEAT_INCOMPAT_NEEDSREPAIR bit set...
> 
>> I wonder if that is because I tried a xfs_repair with a newer version...
> .... which is a result of xfs_repair 6.5.0 crashing mid way through
> repair of the filesystem. Your kernel is too old to recognise the
> NEEDSREPAIR bit. You can clear it with xfs_db like this:
> 
> Run this to get the current field value:
> 
> # xfs_db -c "sb 0" -c "p features_incompat" <dev>
> 
> Then subtract 0x10 from the value returned and run:
> 
> # xfs_db -c "sb 0" -c "write features_incompat <val>" <dev>
> 
> But that won't get you too far - the filesystem is still corrupt and
> inconsistent. By blowing away the log with xfs_repair before
> actually determining if the problem was caused by a RAID array
> issue, you've essentially forced yourself into a filesystem recovery
> situation.

Everything Dave said, yes. Depending on how bad the corruption is, you
*might* be able to do a readonly or readonly/norecovery mount and scrape
some data out.

Ideally the first thing to do would be to make a 1:1 dd image of the
device as a safe backup, but I understand it's 300T ...

-Eric

      parent reply	other threads:[~2024-02-12 22:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 18:39 XFS corruption after power surge/outage Jorge Garcia
2024-02-11 20:39 ` Eric Sandeen
2024-02-12 18:07   ` Jorge Garcia
2024-02-12 21:06     ` Dave Chinner
2024-02-12 21:46       ` Jorge Garcia
2024-02-12 22:39       ` Eric Sandeen [this message]

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=fd31d2df-0378-4337-8841-7d811a8de1d0@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=david@fromorbit.com \
    --cc=jgarcia@soe.ucsc.edu \
    --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).