linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Brendan Hide <brendan@swiftspirit.co.za>
Cc: Omar Sandoval <osandov@fb.com>,
	dsterba@suse.com, fstests@vger.kernel.org,
	linux-btrfs@vger.kernel.org,
	Wang Yanfeng <wangyf-fnst@cn.fujitsu.com>
Subject: Re: [PATCH 2/3] btrfs: add replace missing and replace RAID 5/6 to profile configs
Date: Mon, 27 Jul 2015 22:44:10 +0000	[thread overview]
Message-ID: <20150727224410.GD464@carfax.org.uk> (raw)
In-Reply-To: <55B6AF40.5040107@swiftspirit.co.za>

[-- Attachment #1: Type: text/plain, Size: 2066 bytes --]

On Tue, Jul 28, 2015 at 12:22:56AM +0200, Brendan Hide wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 2015/07/24 07:50 PM, Omar Sandoval wrote:
> > On Fri, Jul 24, 2015 at 02:09:46PM +0200, David Sterba wrote:
> >> On Thu, Jul 23, 2015 at 01:51:50PM -0700, Omar Sandoval wrote:
> >>> +			# We can't do replace with these profiles because they +
> >>> # imply only one device ($SCRATCH_DEV), and we need to +			#
> >>> keep $SCRATCH_DEV around for _scratch_mount +			# and
> >>> _check_scratch_fs. +			local unsupported=( +				"single" +
> >>> "dup"
> >> 
> >> DUP does imply single device, but why does 'single' ?
> > 
> > It does not, I apparently forgot that you could use single to 
> > concatenate multiple devices. I'll fix that in v2.
> > 
> > Thanks for reviewing!
> > 
> Late to the party. DUP *implies* single device but there are cases
> where dup is used on a multi-device fs. Even if the use-cases aren't
> good or intended to be long-term, they are still valid, right?

   Yes, but bear in mind that any new (presumably metadata) chunks
allocated on the multi-device FS will end up as RAID-1, because of the
automatic upgrade from DUP to RAID-1. Any balance will also do the
upgrade.

   Hugo.

PS. Can we get rid of that upgrade? It's a pain the arse in so many
ways.

> - -- 
> __________
> Brendan Hide
> http://swiftspirit.co.za/
> http://www.webafrica.co.za/?AFF1E97
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (MingW32)
> 
> iQEcBAEBAgAGBQJVtq9AAAoJEE+uni74c4qN5eYIAJAGznsi3RD1tchbSLwhMXJk
> bJJ4ORB9taLXHykSfYTsHIaUoVpcVR6tT/I1jz5070DY3mKkQ16a8nwtSxPba4Lv
> QiS8YRegFiHMYzZbH1T7Tnm6R9g/RZsaU7GS3JhP9HUYG7hIWGRRuoiOjYn/hoLw
> uMXuIFOkPKGYDgyAhDIp3KDYlBjMHT6Oun7CcpvTjXiOnzJFFp3MSt3b6mmmdMVV
> YKWpWyKVh7qlENEoqKb4exqr1WGYKU+kBLXRs4wdm3xb66EcWYs0Er1u6v+K1trx
> nryFrfUxYtMJsSuR9ZJm88DOsXKAuX1LEdRKVOlq7krsIK8HlTizccMXAl10gKk=
> =ndkL
> -----END PGP SIGNATURE-----

-- 
Hugo Mills             | I'm on a 30-day diet. So far I've lost 18 days.
hugo@... carfax.org.uk |
http://carfax.org.uk/  |
PGP: E2AB1DE4          |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2015-07-27 22:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 20:51 [PATCH 0/3] xfstests: test btrfs replace on RAID 5/6 Omar Sandoval
2015-07-23 20:51 ` [PATCH 1/3] btrfs/011: test replace on RAID 5/6 now that it's supported Omar Sandoval
2015-07-24  3:01   ` Eryu Guan
2015-07-24 12:10   ` David Sterba
2015-07-23 20:51 ` [PATCH 2/3] btrfs: add replace missing and replace RAID 5/6 to profile configs Omar Sandoval
2015-07-24  3:03   ` Eryu Guan
2015-07-24 12:09   ` David Sterba
2015-07-24 17:50     ` Omar Sandoval
2015-07-27 22:22       ` Brendan Hide
2015-07-27 22:44         ` Hugo Mills [this message]
2015-07-28 16:52         ` David Sterba
2015-07-28 17:41           ` Omar Sandoval
2015-07-23 20:51 ` [PATCH 3/3] btrfs: add a test of replace missing dev in diff raid Omar Sandoval
2015-07-24  3:28   ` Eryu Guan
2015-07-24 17:52     ` Omar Sandoval

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=20150727224410.GD464@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=brendan@swiftspirit.co.za \
    --cc=dsterba@suse.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=osandov@fb.com \
    --cc=wangyf-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).