From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Scrub priority, am I using it wrong?
Date: Tue, 5 Apr 2016 04:19:11 +0000 (UTC) [thread overview]
Message-ID: <pan$1084d$87b30d83$4860fe5b$19700f4b@cox.net> (raw)
In-Reply-To: CA+WRLO_fkZWsZJFdvMQud1aMTR7kErJVxr9JT0vNpjhQrh2e2Q@mail.gmail.com
Gareth Pye posted on Tue, 05 Apr 2016 13:44:05 +1000 as excerpted:
> On Tue, Apr 5, 2016 at 12:37 PM, Duncan <1i5t5.duncan@cox.net> wrote:
>> 1) It appears btrfs scrub start's -c option only takes numeric class,
>> so try -c3 instead of -c idle.
>
>
> Does it count as a bug if it silently accepts the way I was doing it?
>
> I've switched to -c3 and at least now the idle class listed in iotop is
> idle, so I hope that means it will be more friendly to other processes.
I'd say yes, particularly given that the value must be the numeric class
isn't documented in the manpage at all.
Whether the bug is then one of documentation (say it must be numeric) or
of implementation (take the class name as well) is then up for debate.
I'd call fixing either one a fix. If it must be numeric, document that
(and optionally change the implementation to error in some way if a
numeric parameter isn't supplied for -c), else change the implementation
so the name can be taken as well (and optionally change the documentation
to explicitly mention that either one can be used). Doesn't matter to me
which.
--
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-05 4:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 23:36 Scrub priority, am I using it wrong? Gareth Pye
2016-04-05 2:37 ` Duncan
2016-04-05 3:44 ` Gareth Pye
2016-04-05 4:19 ` Duncan [this message]
2016-04-05 11:44 ` Austin S. Hemmelgarn
2016-04-05 3:45 ` Gareth Pye
2016-04-05 4:25 ` Duncan
2016-04-05 17:34 ` Henk Slager
2016-04-06 0:00 ` Gareth Pye
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$1084d$87b30d83$4860fe5b$19700f4b@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 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).