public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
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 14:17:08 +0000	[thread overview]
Message-ID: <20200217141708.GE1235@savella.carfax.org.uk> (raw)
In-Reply-To: <CAJVZm6dyD1w6i6oRECGMhVOZcEH7OQvS_fP5bOyC3C7ZEi6Omg@mail.gmail.com>

On Mon, Feb 17, 2020 at 03:12:35PM +0100, Menion wrote:
> ok thanks
> I have launched it (in a tmux session), after 5 minutes the command
> did not return yet, but dmesg and  btrfs balance status
> /array/mount/point report it in progress (0%).
> Is it normal?

   Yes, it's got to rewrite all of your metadata. This can take a
while (especially if you have lots of snapshots or reflinks -- such as
from running a deduper). You should be able to see progress happening
fairly regularly in dmesg. This is typically one chunk every minute or
so, although some chunks can take much *much* longer.

   Hugo.

> Il giorno lun 17 feb 2020 alle ore 14:55 Swâmi Petaramesh
> <swami@petaramesh.org> ha scritto:
> >
> > On 2020-02-17 14:50, Menion wrote:
> > > Is it ok to run it on a mounted filesystem with concurrent read and
> > > write operations?
> >
> > Yes. Please check man btrfs-balance.
> >
> > All such BTRFS operations are to be run on live, mounted filesystems.
> >
> > Performance will suffer and it might be long though.
> >
> > > Also, since the number of HDD is 5, how this "raid1" scheme is deployed?
> >
> > BTRFS will manage storing 2 copies of every metadata block on 2
> > different disks, and will choose how by itself.
> >
> > ॐ
> >

-- 
Hugo Mills             | You've read the project plan. Forget that. We're
hugo@... carfax.org.uk | going to Do Stuff and Have Fun doing it.
http://carfax.org.uk/  |
PGP: E2AB1DE4          |                                           Jeremy Frey

  reply	other threads:[~2020-02-17 14:17 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
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 [this message]
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=20200217141708.GE1235@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