From: Johannes Thumshirn <jthumshirn@suse.de>
To: Nikolay Borisov <nborisov@suse.com>, David Sterba <dsterba@suse.com>
Cc: rbrown@suse.de, Linux BTRFS Mailinglist <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs-progs: warn users about the possible dangers of check --repair
Date: Thu, 17 Oct 2019 09:13:50 +0200 [thread overview]
Message-ID: <a964ba85-877a-8bd7-2740-604b5f938b32@suse.de> (raw)
In-Reply-To: <0b32b2d3-e473-dcbd-57b9-036b9505d145@suse.com>
On 16/10/2019 16:31, Nikolay Borisov wrote:
[...]
>> + printf("\tfsck successfully repair all types of filesystem corruption. Eg.\n");
>> + printf("\tsome other software or hardware bugs can fatally damage a volume.\n");
>
> nit: The word 'other' here is redundant, no ?
Hmm really, maybe. But the sentence above lacks a 'can' (I'll fix it up
in the manpage as well.
>
>> + printf("\tThe operation will start in %d seconds.\n", delay);
>> + printf("\tUse Ctrl-C to stop it.\n");
>> + while (delay) {
>> + printf("%2d", delay--);
>> + fflush(stdout);
>> + sleep(1);
>> + }
>
> That's a long winded way to have a simple for loop that prints 10 dots,
> 1 second apart. IMO a better use experience would be to ask the user to
> confirm and if the '-f' options i passed don't bother printing the
> warning at all.
That's just copy & paste from cmds/balance.c
--
Johannes Thumshirn SUSE Labs Filesystems
jthumshirn@suse.de +49 911 74053 689
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5
90409 Nürnberg
Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
prev parent reply other threads:[~2019-10-17 7:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 14:05 [PATCH] btrfs-progs: warn users about the possible dangers of check --repair Johannes Thumshirn
2019-10-16 14:18 ` Qu Wenruo
2019-10-16 14:31 ` Nikolay Borisov
2019-10-17 1:25 ` Anand Jain
2019-10-17 6:40 ` Nikolay Borisov
2019-10-17 7:10 ` Johannes Thumshirn
2019-10-17 7:13 ` Johannes Thumshirn [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=a964ba85-877a-8bd7-2740-604b5f938b32@suse.de \
--to=jthumshirn@suse.de \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=rbrown@suse.de \
/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