From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: 3.13.5 kernel hangs some processes with btrfs
Date: Mon, 24 Feb 2014 06:42:30 +0000 (UTC) [thread overview]
Message-ID: <pan$5eb48$855696ce$5bb0f0dc$b9ce161e@cox.net> (raw)
In-Reply-To: 20140224061714.GC15937@merlins.org
Marc MERLIN posted on Sun, 23 Feb 2014 22:17:14 -0800 as excerpted:
> Mmmh, this bug might be part of the problem:
> gargamel:/mnt# btrfs scrub start btrfs_pool2
> ERROR: scrub is already running.
> gargamel:/mnt# btrfs scrub cancel btrfs_pool2
> ERROR: scrub cancel failed on btrfs_pool2: not running
> gargamel:/mnt# btrfs scrub status
[snip output]
> Note that it says running for 5 seconds, but it started 4H ago.
This is a known issue.
I believe there's a fix coming (a cancel that blows away the tracking
file if it finds it and no actual running scrub is the most obvious fix),
but meanwhile, see the /var/lib/btrfs/scrub.status.* files. That's where
scrub state is stored, and manually blowing away the appropriate file
should clear btrfs' memory of the aborted scrub, so you can scrub start
properly.
--
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:[~2014-02-24 6:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 6:14 3.13.5 kernel hangs some processes with btrfs Marc MERLIN
2014-02-24 6:17 ` Marc MERLIN
2014-02-24 6:27 ` Wang Shilong
2014-02-24 6:42 ` Marc MERLIN
2014-02-24 6:42 ` Duncan [this message]
2014-02-24 6:58 ` Marc MERLIN
2014-02-24 7:18 ` Wang Shilong
2014-02-24 7:29 ` Duncan
2014-02-24 17:35 ` Marc MERLIN
2014-02-25 5:31 ` 3.14rc3 kernel also " Marc MERLIN
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$5eb48$855696ce$5bb0f0dc$b9ce161e@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.