From: Marc Joliet <marcec@gmx.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs scrub status reports not running when it is
Date: Wed, 14 Jan 2015 22:23:34 +0100 [thread overview]
Message-ID: <20150114222334.5f207a5d@marcec.fritz.box> (raw)
In-Reply-To: <CAPs0BijZX-BcM7uRq58TwSUqsNRqsySXeHYRezgVQcfXw-d22g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
Am Wed, 14 Jan 2015 16:06:02 -0500
schrieb Sandy McArthur Jr <sandymac@gmail.com>:
> Sometimes btrfs scrub status reports that is not running when it still is.
[...]
FWIW, I (and one other person) reported this in the thread titled 'btrfs scrub
status misreports as "interrupted"' (starting on 22.11.2014).
> # uname -a
> Linux mcplex 3.18.2-gentoo #1 SMP Mon Jan 12 10:24:25 EST 2015 x86_64
> Intel(R) Core(TM) i7-2600S CPU @ 2.80GHz GenuineIntel GNU/Linux
>
> # btrfs --version
> Btrfs v3.18.1
Too bad it's still there; I'm on kernel 3.17.8 and userspace 3.18.1,
respectively, and didn't see this issue the last time I ran a scrub, so I was
hoping it was gone by now.
(On the upside, though, this isn't exactly the worst bug btrfs has ever
had ;) .)
Greetings
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-01-14 21:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 21:06 btrfs scrub status reports not running when it is Sandy McArthur Jr
2015-01-14 21:23 ` Marc Joliet [this message]
2015-01-14 21:26 ` Sandy McArthur Jr
2015-01-14 22:27 ` Zach Brown
2015-01-15 11:24 ` David Sterba
2015-01-15 18:02 ` Zach Brown
2015-01-19 17:45 ` David Sterba
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=20150114222334.5f207a5d@marcec.fritz.box \
--to=marcec@gmx.de \
--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).