From: Pierre Abbat <phma@bezitopo.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: Trying to mount hangs
Date: Fri, 22 May 2020 05:40:36 -0400 [thread overview]
Message-ID: <2582603.WkyslYimHe@puma> (raw)
In-Reply-To: <290f9ee7-1aed-2a92-bdba-063d238bd5bc@gmx.com>
On Thursday, May 21, 2020 9:32:54 PM EDT Qu Wenruo wrote:
> Considering your btrfs check reports no serious problem, the hang looks
> strange.
>
> The remaining possibility is the log tree.
>
> You could try to boot using any liveCD with new enough kernel, then
> btrfs ins dump-super <device> | grep log_root
I can do that booted normally from the M.2. The output is
log_root 862339072
log_root_transid 0
log_root_level 0
> If the result is not 0, then try btrfs rescue zero-log, then try mount
> again.
You seem to be misunderstanding me. I'm not trying to fix the broken filesystem;
I already recovered the files to a new drive. I'm trying to give you enough
information to reproduce the hang in mount, so that you can fix the bug. If I
have to copy the entire filesystem to an external drive and ship it, I'll do
that, but I'm hoping that some smaller amount of data that I can upload in a
few hours would be sufficient.
When I write a function that reads a file of a certain format, unless it's a
static file like a list of all primes less than 65536 with associated data, I
fuzz it so that, if it's given a file that's not exactly in that format, it
won't hang or crash.
Pierre
--
li fi'u vu'u fi'u fi'u du li pa
next prev parent reply other threads:[~2020-05-22 9:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 1:34 Trying to mount hangs Pierre Abbat
2020-05-21 7:56 ` Qu Wenruo
2020-05-21 23:48 ` Pierre Abbat
2020-05-22 1:32 ` Qu Wenruo
2020-05-22 9:40 ` Pierre Abbat [this message]
2020-05-22 10:02 ` Qu Wenruo
2020-05-24 6:37 ` Pierre Abbat
2020-05-24 9:24 ` Qu Wenruo
2020-05-24 12:10 ` Pierre Abbat
2020-05-24 12:32 ` Qu Wenruo
2020-05-27 10:41 ` Qu Wenruo
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=2582603.WkyslYimHe@puma \
--to=phma@bezitopo.org \
--cc=linux-btrfs@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).