From: Johannes Thumshirn <jthumshirn@suse.de>
To: David Sterba <dsterba@suse.com>
Cc: Nikolay Borisov <nborisov@suse.com>,
quwenruo.btrfs@gmx.com, anand.jain@oracle.com, rbrown@suse.de,
Linux BTRFS Mailinglist <linux-btrfs@vger.kernel.org>,
Johannes Thumshirn <jthumshirn@suse.de>
Subject: [PATCH v2 2/2] btrfs-progs: docs: fix warning test
Date: Fri, 18 Oct 2019 13:16:04 +0200 [thread overview]
Message-ID: <20191018111604.16463-2-jthumshirn@suse.de> (raw)
In-Reply-To: <20191018111604.16463-1-jthumshirn@suse.de>
The warning about the dangers of repair was lacking a bit grammatically odd.
Fix it to read more naturally.
Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
---
Documentation/btrfs-check.asciidoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/btrfs-check.asciidoc b/Documentation/btrfs-check.asciidoc
index b963eae5cdce..1a4d8167ccba 100644
--- a/Documentation/btrfs-check.asciidoc
+++ b/Documentation/btrfs-check.asciidoc
@@ -23,8 +23,8 @@ by the option '--readonly'.
*btrfsck* is an alias of *btrfs check* command and is now deprecated.
WARNING: Do not use '--repair' unless you are advised to do so by a developer
-or an experienced user, and then only after having accepted that no 'fsck'
-successfully repair all types of filesystem corruption. Eg. some other software
+or an experienced user, and then only after having accepted that no 'fsck' can
+successfully repair all types of filesystem corruption. Eg. some software
or hardware bugs can fatally damage a volume.
The structural integrity check verifies if internal filesystem objects or
--
2.16.4
next prev parent reply other threads:[~2019-10-18 11:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 11:16 [PATCH v2 1/2] btrfs-progs: warn users about the possible dangers of check --repair Johannes Thumshirn
2019-10-18 11:16 ` Johannes Thumshirn [this message]
2019-10-21 15:22 ` David Sterba
2019-10-22 7:33 ` Johannes Thumshirn
2019-10-22 7:37 ` Qu Wenruo
2019-10-22 7:45 ` Johannes Thumshirn
2019-10-22 7:50 ` Nikolay Borisov
2019-10-22 12:19 ` David Sterba
2019-11-15 12:53 ` David Sterba
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=20191018111604.16463-2-jthumshirn@suse.de \
--to=jthumshirn@suse.de \
--cc=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=quwenruo.btrfs@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.