From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Help ! "btrfs check" looping recursive
Date: Fri, 15 Apr 2016 00:24:21 +0000 (UTC) [thread overview]
Message-ID: <pan$9e5b6$4adde6c7$caa17ba5$f91d4445@cox.net> (raw)
In-Reply-To: 570FCBBD.2010500@petaramesh.org
Swâmi Petaramesh posted on Thu, 14 Apr 2016 18:56:29 +0200 as excerpted:
> It seems that i have a "btrfs check" process that’s stuck in an infinite
> recursive loop…
>
> How could I end this without breaking my filesystem ?
...
> root@PartedMagic:~# btrfs check --repair /dev/VGZ/LINUX
> enabling repair mode [...]
[Just a btrfs user and list regular myself, not a btrfs dev and not at a
level to specifically answer the question.]
Given the prompt above, you're running from parted-magic, but that
doesn't tell us the btrfs-progs or kernel versions unless we look it up.
So kernel and btrfs-progs version? Also, btrfs filesystem show output
might be useful.
(Tho in this specific context, kernel version isn't as useful as normal,
since unlike many btrfs commands that simply call kernel code to do the
real work, check code is all userspace. But it's can't hurt to post it.
Similarly, btrfs fi df to compliment btrfs fi show, or btrfs fi usage to
output the same information as both, would in other contexts be useful,
but they require a mounted filesystem, not something you can really even
try with check running.)
Btrfs-progs version in particular, since the recursive nature of this
loop is very obviously a bug. If it's a current progs version, the bug
may have been recently introduced. If it's a dated version, the bug may
have already been fixed. (Either way, it may be that someone else will
recognize the bug and tell you to try a later/earlier version, or if not,
you very well may prompt a new patch, possibly after some further
debugging.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-04-15 0:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 16:56 Help ! "btrfs check" looping recursive Swâmi Petaramesh
2016-04-15 0:24 ` Duncan [this message]
2016-04-15 9:13 ` Swâmi Petaramesh
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='pan$9e5b6$4adde6c7$caa17ba5$f91d4445@cox.net' \
--to=1i5t5.duncan@cox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.