From: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
To: Graham Cobb <g.btrfs@cobb.uk.net>
Cc: Goffredo Baroncelli <kreijack@libero.it>,
linux-btrfs@vger.kernel.org, Qu Wenruo <quwenruo.btrfs@gmx.com>,
David Sterba <dsterba@suse.com>
Subject: Re: [PATCH v2] btrfs-progs: add warning for mixed profiles filesystem
Date: Tue, 31 Mar 2020 18:05:37 -0400 [thread overview]
Message-ID: <20200331220534.GI2693@hungrycats.org> (raw)
In-Reply-To: <97ec9f13-8d8d-1df9-f725-44a2a0ecc438@cobb.uk.net>
On Tue, Mar 31, 2020 at 10:46:17PM +0100, Graham Cobb wrote:
> On 31/03/2020 20:10, Goffredo Baroncelli wrote:
> > WARNING: ------------------------------------------------------
> > WARNING: Detection of multiple profiles for a block group type:
> > WARNING:
> > WARNING: * DATA -> [raid1c3, single]
> > WARNING: * METADATA -> [raid1, single]
> > WARNING:
> > WARNING: Please consider using 'btrfs balance ...' commands set
> > WARNING: to solve this issue.
> > WARNING: ------------------------------------------------------
>
> The check is a good a idea but I think the warning is too strong. I
> would prefer that the word "Warning" is reserved for cases and
> operations that may actually damage data (such as reformating a
> filesystem). [Note: in a previous job, my employer decided that the word
> Warning was ONLY to be used if there was a risk of harm to a human - for
> example, electrical safety]
>
> Also, btrfs fi usage is something that I routinely run continuously in a
> window (using watch) when a remove/replace/balance operation is in
I was going to say please put all the new output lines at the bottom,
so that 'watch' windows can be minimally sized without having to write
something like
watch 'btrfs fi usage /foo | sed -e "g/WARNING:/d"'
People with short terminal windows running btrfs fi usage directly from
the command line would probably complain about extra lines at the bottom...
Another good idea here would be a --quiet switch, or
'--no-profile-warning'.
> progress to monitor at a glance what is happening - I don't want to
> waste all that space on the screen. To say nothing of the annoyance of
> having it shouting at me for weeks on end while **I AM TRYING TO FIX THE
> DAMN PROBLEM!**.
>
> I would suggest a more compact layout and factual tone. Something like:
>
> Caution: This filesystem has multiple profiles for a block group type
> so new block groups will have unpredictable profiles.
> * DATA -> [raid1c3, single]
> * METADATA -> [raid1, single]
> Use of 'btrfs balance' is recommended as soon as possible to move all
> blocks to a single profile for each of data and metadata.
How about a one-liner:
NOTE: Multiple profiles detected. See 'man btrfs-filesystem'.
with a section in the btrfs-filesystem man page giving a detailed
description of the problem and examples of possible remedies.
next prev parent reply other threads:[~2020-03-31 22:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 19:10 [PATCH v2] btrfs-progs: add warning for mixed profiles filesystem Goffredo Baroncelli
2020-03-31 19:10 ` [PATCH 1/4] Complete the implementation of RAID1C[34] Goffredo Baroncelli
2020-03-31 19:10 ` [PATCH 2/4] btrfs-progs: Add BTRFS_EXTENDED_PROFILE_MASK mask Goffredo Baroncelli
2020-03-31 19:10 ` [PATCH 3/4] btrfs-progs: Add btrfs_check_for_mixed_profiles_by_* function Goffredo Baroncelli
2020-03-31 19:10 ` [PATCH 4/4] btrfs-progs: Add mixed profiles check to some btrfs sub-commands Goffredo Baroncelli
2020-03-31 21:46 ` [PATCH v2] btrfs-progs: add warning for mixed profiles filesystem Graham Cobb
2020-03-31 22:05 ` Zygo Blaxell [this message]
2020-04-01 10:58 ` Graham Cobb
2020-04-01 17:15 ` Goffredo Baroncelli
2020-04-01 18:20 ` David Sterba
2020-04-01 19:05 ` Goffredo Baroncelli
2020-04-01 18:25 ` 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=20200331220534.GI2693@hungrycats.org \
--to=ce3g8jdj@umail.furryterror.org \
--cc=dsterba@suse.com \
--cc=g.btrfs@cobb.uk.net \
--cc=kreijack@libero.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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