From: Robert White <rwhite@pobox.com>
To: Bob Williams <linux@barrowhillfarm.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: scrub problem
Date: Sun, 22 Feb 2015 10:26:34 -0800 [thread overview]
Message-ID: <54EA1F5A.7010802@pobox.com> (raw)
In-Reply-To: <54E7A128.1060603@barrowhillfarm.org.uk>
On 02/20/2015 01:03 PM, Bob Williams wrote:
> /var/lib/btrfs/scrub.status.0b07b829-9a0e-44ab-89ee-14b36a45199e
>
> (the last bit of the filename is the filesystem uuid)
>
> Look for a line that ends with "finished:0" and change it to say
> "finished:1"
Why does this data item even exist? The filesystem/kernel should know
whether a scrub is ongoing. Isn't is universally cheaper to do the
single IOCTL to ask the kernel whether a scrub is ongoing compared to
the open-and-parse of this file?
next prev parent reply other threads:[~2015-02-22 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 19:59 scrub problem Johan Kröckel
2015-02-20 21:03 ` Bob Williams
2015-02-22 18:26 ` Robert White [this message]
2015-02-24 2:11 ` Anand Jain
-- strict thread matches above, loose matches on Subject: below --
2015-02-20 22:46 Calvin Walton
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=54EA1F5A.7010802@pobox.com \
--to=rwhite@pobox.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux@barrowhillfarm.org.uk \
/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).