linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Su Yue" <Damenly_Su@gmx.com>
To: "Nikolay Borisov" <nborisov@suse.com>
Cc: "Su Yue" <suy.fnst@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH RFC 0/3] btrfs-progs: lowmem: delay before lowmem repair
Date: Mon, 2 Jul 2018 16:01:26 +0200	[thread overview]
Message-ID: <trinity-d938775a-abc7-4647-9ffc-0d69a56e37e7-1530540086745@3c-app-mailcom-bs10> (raw)
In-Reply-To: <93c08062-8368-616f-f8c6-5ff8616aad08@suse.com>



> Sent: Monday, July 02, 2018 at 5:43 PM
> From: "Nikolay Borisov" <nborisov@suse.com>
> To: "Su Yue" <suy.fnst@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
> Subject: Re: [PATCH RFC 0/3] btrfs-progs: lowmem: delay before lowmem repair
>
> 
> 
> On  2.07.2018 12:28, Su Yue wrote:
> > Since lowmem repair is dangerous, it should remind user more obviously.
> > The patchset add 10 seconds delay like btrfs balance and add am option
> > '--force-repair-lowmem' to skip the delay.
> 
> IMO this is the wrong way to approach a dangerous option. If it's so
> dangerous it needs to be written in the documentation explicitly this is
> so. If someone wants to use lowmem then they should explicitly set
> --mode lowmem. So I'm inclined to NACK this patch.
> 
OK. After some considerations, I thinks the patchset is indeed appropriate.
Droping it is fine.

Thanks,
Su
> > 
> > ---
> > I don't whether it's a good idea to add delay and the option only for
> > lowmem repair is acceptable, so make it RFC.
> > 
> > Su Yue (3):
> >   btrfs-progs: lowmem: delay before lowmem repair starts
> >   btrfs-progs: lowmem: force to start without delay with option
> >     '--force-repair-lowmem'
> >   btrfs-progs: tests: append '--force-repair-lowmem' if lowmem repair is
> >     enabled
> > 
> >  check/main.c       | 43 ++++++++++++++++++++++++++++++++++++-------
> >  tests/common.local |  1 +
> >  2 files changed, 37 insertions(+), 7 deletions(-)
> > 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

      parent reply	other threads:[~2018-07-02 14:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02  9:28 [PATCH RFC 0/3] btrfs-progs: lowmem: delay before lowmem repair Su Yue
2018-07-02  9:28 ` [PATCH RFC 1/3] btrfs-progs: lowmem: delay before lowmem repair starts Su Yue
2018-07-02  9:28 ` [PATCH RFC 2/3] btrfs-progs: lowmem: force to start without delay with option '--force-repair-lowmem' Su Yue
2018-07-02  9:28 ` [PATCH RFC 3/3] btrfs-progs: tests: append '--force-repair-lowmem' if lowmem repair is enabled Su Yue
2018-07-02  9:43 ` [PATCH RFC 0/3] btrfs-progs: lowmem: delay before lowmem repair Nikolay Borisov
2018-07-02 11:07   ` David Disseldorp
2018-07-02 11:09     ` Nikolay Borisov
2018-07-02 13:57       ` Su Yue
2018-07-02 14:01   ` Su Yue [this message]

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=trinity-d938775a-abc7-4647-9ffc-0d69a56e37e7-1530540086745@3c-app-mailcom-bs10 \
    --to=damenly_su@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.com \
    --cc=suy.fnst@cn.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;
as well as URLs for NNTP newsgroup(s).