From: John Jore <john@jore.no>
To: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>
Subject: Re: Bug in xfs_repair 5..4.0 / Unable to repair metadata corruption
Date: Mon, 10 Feb 2020 10:33:06 +0000 [thread overview]
Message-ID: <5f80fcd0870145579310ca347931fbd6@jore.no> (raw)
In-Reply-To: <60f32c031f4345a2b680fbc8531f7bd3@jore.no>
Hi and no, that message appears when -d is used, even if the volume is not mounted (at least on the current version from git)
The help page states this for -d, given that the metadata corruption could not be repaired without the option, I gave it a try (there is no mention that this supports mounted volumes?):
-d Repair dangerously.
John
----
From: Eric Sandeen <sandeen@sandeen.net>
Sent: 10 February 2020 14:49
To: John Jore; linux-xfs@vger.kernel.org
Subject: Re: Bug in xfs_repair 5..4.0 / Unable to repair metadata corruption
On 2/9/20 9:47 PM, Eric Sandeen wrote:
> On 2/9/20 12:19 AM, John Jore wrote:
...
>> Does not matter how many times, I've lost count, I re-run xfs_repair, with, or without -d,
>
> -d is for repairing a filesystem while mounted. I hope you are not doing that, are you?
"Repair of readonly mount complete. Immediate reboot encouraged."
er, maybe you are. Why?
-Eric
next prev parent reply other threads:[~2020-02-10 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <186d30f217e645728ad1f34724cbe3e7@jore.no>
2020-02-09 6:19 ` Bug in xfs_repair 5..4.0 / Unable to repair metadata corruption John Jore
2020-02-10 3:47 ` Eric Sandeen
2020-02-10 3:49 ` Eric Sandeen
[not found] ` <60f32c031f4345a2b680fbc8531f7bd3@jore.no>
2020-02-10 10:33 ` John Jore [this message]
2020-02-10 14:36 ` Eric Sandeen
2020-02-10 14:43 ` Eric Sandeen
2020-02-10 15:35 ` Eric Sandeen
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=5f80fcd0870145579310ca347931fbd6@jore.no \
--to=john@jore.no \
--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