public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
Cc: Rory Campbell-Lange <rory@campbell-lange.net>,
	linux-btrfs@vger.kernel.org
Subject: Re: trouble replacing second disk from pair
Date: Wed, 8 Dec 2021 23:15:31 +0500	[thread overview]
Message-ID: <20211208231531.27379888@nvm> (raw)
In-Reply-To: <20211208180140.GN17148@hungrycats.org>

On Wed, 8 Dec 2021 13:01:40 -0500
Zygo Blaxell <ce3g8jdj@umail.furryterror.org> wrote:

> -m implies -s.  In normal use, there is never a reason to have different
> profiles for metadata and system

Then there appears to be no reason to have "system" user-visible as a separate
chunk type.

-- 
With respect,
Roman

      reply	other threads:[~2021-12-08 18:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08 12:40 trouble replacing second disk from pair Rory Campbell-Lange
2021-12-08 13:09 ` Roman Mamedov
2021-12-08 17:21   ` Rory Campbell-Lange
2021-12-08 18:01     ` Zygo Blaxell
2021-12-08 18:15       ` Roman Mamedov [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=20211208231531.27379888@nvm \
    --to=rm@romanrm.net \
    --cc=ce3g8jdj@umail.furryterror.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rory@campbell-lange.net \
    /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