From: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
To: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 4/4] btrfs-progs: correct manpage option description for scrub
Date: Wed, 30 Jul 2014 13:39:38 +0800 [thread overview]
Message-ID: <1406698778.30821.8.camel@localhost.localdomain> (raw)
In-Reply-To: <53D8808E.4020609@jp.fujitsu.com>
On Wed, 2014-07-30 at 14:20 +0900, Satoru Takeuchi wrote:
> Hi Gui,
>
> (2014/07/17 11:40), Gui Hecheng wrote:
> > The -f option of scrub means to skip checking running scrub,
> > not to force checking.
> >
> > Signed-off-by: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
> > ---
> > Documentation/btrfs-scrub.txt | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/btrfs-scrub.txt b/Documentation/btrfs-scrub.txt
> > index 7b27d63..1af9b9f 100644
> > --- a/Documentation/btrfs-scrub.txt
> > +++ b/Documentation/btrfs-scrub.txt
> > @@ -47,7 +47,7 @@ manpage).
> > -n <ioprio_classdata>::::
> > Set IO priority classdata (see `ionice`(1) manpage).
> > -f::::
> > -force to check whether scrub has started or resumed in userspace.
> > +force to skip checking whether scrub has started or resumed in userspace.
Hi Satoru,
Thanks for your comments first. My opinions are as follows:
> I consider "scrub has started and resumed" is not user-friendly
> expression. First, it can be replaced with more easy one,
> "scrub is running". Second, there in no explanation about
> this checking behavior before "-f" option's description.
Yes, "Scrub is running" is more precise.
> So, how about the following idea?
>
> Fix 1. Add "If scrub is already running running, it fails."
> to the description before `Options` section
This is really a valuable idea.
> Fix 2. Replace "force to check ..." with
> "force starting new scrub even if scrub is already running."
This is more precise.
> Fix 3. Fix cmd_scrub_start_usage too.
Of course, thanks for reminding me.
So please let me rework this patch, could I add your sign-off-by then?
Thanks,
Gui
>
> Thanks,
> Satoru
>
> > this is useful when scrub stat record file is damaged.
> >
> > *cancel* <path>|<device>::
> >
>
next prev parent reply other threads:[~2014-07-30 5:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 2:40 [PATCH 1/4] btrfs-progs: adjust the return values for scrub Gui Hecheng
2014-07-17 2:40 ` [PATCH 2/4] btrfs-progs: remove unnecessary judgment for fd in scrub Gui Hecheng
2014-07-30 6:07 ` Satoru Takeuchi
2014-07-17 2:40 ` [PATCH 3/4] btrfs-progs: replace a confusing raw number with a macro Gui Hecheng
2014-07-29 12:16 ` David Sterba
2014-07-29 12:19 ` David Sterba
2014-07-30 1:17 ` Gui Hecheng
2014-07-17 2:40 ` [PATCH 4/4] btrfs-progs: correct manpage option description for scrub Gui Hecheng
2014-07-30 5:20 ` Satoru Takeuchi
2014-07-30 5:39 ` Gui Hecheng [this message]
2014-07-30 6:09 ` Satoru Takeuchi
2014-07-30 7:32 ` [PATCH v2] " Gui Hecheng
2014-07-30 10:26 ` Duncan
2014-07-31 1:25 ` Gui Hecheng
2014-07-31 12:24 ` David Sterba
2014-07-30 6:03 ` [PATCH 1/4] btrfs-progs: adjust the return values " Satoru Takeuchi
2014-07-30 6:36 ` Satoru Takeuchi
2014-07-30 7:27 ` Gui Hecheng
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=1406698778.30821.8.camel@localhost.localdomain \
--to=guihc.fnst@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=takeuchi_satoru@jp.fujitsu.com \
/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