From: iamdooser <iamdooser@gmail.com>
To: Eric Sandeen <sandeen@redhat.com>, linux-xfs@vger.kernel.org
Subject: Re: xfs_repair hangs at "process newly discovered inodes..."
Date: Sat, 19 Nov 2022 12:24:18 -0500 [thread overview]
Message-ID: <8ed7c0ee-dd04-8346-87cb-83c2222f3454@gmail.com> (raw)
In-Reply-To: <39028244-fec6-6717-d8a7-b9f89f5a1f3b@redhat.com>
Thank you for responding.
Yes that found errors, although I'm not accustomed to interpreting the
output.
xfs_repair version 5.18.0
The output of xfs_repair -nv was quite large, as was the
xfs_metadump...not sure that's indicative of something, but I've
uploaded them here:
https://drive.google.com/drive/folders/1OyQOZNsTS1w1Utx1ZfQEH-bS_Cyj8-F2?usp=sharing
There doesn't seem to be much activity once it hangs at "process newly
discovered inodes..." so it doesn't seem like just a slow repair.
Desipte there being no sign of activity, I've let it run for 24+ hours
and saw no changes..
On 11/17/22 13:48, Eric Sandeen wrote:
> On 11/17/22 12:40 PM, iamdooser wrote:
>> Hello,
>>
>> I'm not sure this is the correct forum; if not I'd appreciate guidance.
>>
>> I have a Unraid machine that experienced an unmountable file system on an array disc. Running:
>>
>> xfs_repair -nv /dev/md3
>
> Did that find errors?
>
>> works, however when running
>>
>> xfs_repair -v /dev/md3
>>
>> it stops at "process newly discovered inodes..." and doesn't seem to be doing anything.
>>
>> I've asked in the unraid forum and they've directed me to the xfs mailing list.
>>
>> Appreciate any help.
>
> Please tell us the version of xfsprogs you're using, and provide the full xfs_repair
> output (with and without -n).
>
> If it really looks like a bug, and not simply a slow repair, providing an xfs_metadump
> may help us evaluate the problem further.
>
> -Eric
>
next prev parent reply other threads:[~2022-11-19 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 18:40 xfs_repair hangs at "process newly discovered inodes..." iamdooser
2022-11-17 18:48 ` Eric Sandeen
2022-11-19 17:24 ` iamdooser [this message]
2022-11-21 16:14 ` Carlos Maiolino
2022-11-21 16:24 ` Eric Sandeen
2022-11-21 20:48 ` Dave Chinner
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=8ed7c0ee-dd04-8346-87cb-83c2222f3454@gmail.com \
--to=iamdooser@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.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