From: Hugo Mills <hugo@carfax.org.uk>
To: Menion <menion@gmail.com>
Cc: "Swâmi Petaramesh" <swami@petaramesh.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs: convert metadata from raid5 to raid1
Date: Mon, 17 Feb 2020 13:55:42 +0000 [thread overview]
Message-ID: <20200217135542.GD1235@savella.carfax.org.uk> (raw)
In-Reply-To: <CAJVZm6fj9V7G2zLjNpR5MRcZOke0NxydWm1aMY44n2L18fP04w@mail.gmail.com>
On Mon, Feb 17, 2020 at 02:51:12PM +0100, Menion wrote:
> Also, since the number of HDD is 5, how this "raid1" scheme is deployed?
Two copies of any one piece of data, each copy on a separate
device.
Hugo.
> Il giorno lun 17 feb 2020 alle ore 14:50 Menion <menion@gmail.com> ha scritto:
> >
> > Is it ok to run it on a mounted filesystem with concurrent read and
> > write operations?
> >
> > Il giorno lun 17 feb 2020 alle ore 14:49 Swâmi Petaramesh
> > <swami@petaramesh.org> ha scritto:
> > >
> > > Hi,
> > >
> > > On 2020-02-17 14:43, Menion wrote:
> > > > What is the correct procedure to convert metadata from raid5 to proper
> > > > raid scheme (raid1 or)?
> > >
> > > # btrfs balance start -mconvert=raid1 /array/mount/point should do the trick
> > >
> > > ॐ
> > >
--
Hugo Mills | Turning, pages turning in the widening bath,
hugo@... carfax.org.uk | The spine cannot bear the humidity.
http://carfax.org.uk/ | Books fall apart; the binding cannot hold.
PGP: E2AB1DE4 | Page 129 is loosed upon the world. Zarf
next prev parent reply other threads:[~2020-02-17 13:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 13:43 btrfs: convert metadata from raid5 to raid1 Menion
2020-02-17 13:49 ` Swâmi Petaramesh
2020-02-17 13:50 ` Menion
2020-02-17 13:51 ` Menion
2020-02-17 13:55 ` Hugo Mills [this message]
2020-02-17 13:54 ` Hugo Mills
2020-02-17 13:55 ` Swâmi Petaramesh
2020-02-17 14:12 ` Menion
2020-02-17 14:17 ` Hugo Mills
2020-02-17 18:05 ` Graham Cobb
2020-02-18 8:34 ` Menion
2020-02-18 8:41 ` Nikolay Borisov
2020-02-18 8:43 ` Menion
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=20200217135542.GD1235@savella.carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=menion@gmail.com \
--cc=swami@petaramesh.org \
/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