Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: "Miguel Sousa Filipe" <miguel.filipe@gmail.com>
To: "Chris Mason" <chris.mason@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Online device removal pushed to the unstable tree
Date: Wed, 14 May 2008 15:41:53 +0100	[thread overview]
Message-ID: <f058a9c30805140741o7d4c4e67l243f981d1b750cca@mail.gmail.com> (raw)
In-Reply-To: <200805131608.36386.chris.mason@oracle.com>

Hi all,

On Tue, May 13, 2008 at 9:08 PM, Chris Mason <chris.mason@oracle.com> wrote:
> Hello everyone,
>
>  The unstable tree is still format compatible with v0.14, and it now includes
>  the ability to remove devices online.  In mirror configurations, IO errors to
>  one of the mirrors are also handled, although it doesn't currently kick off a
>  rebuild or other magic.
>
>  To try things out:
>
>  mkfs.btrfs -d raid1 -m raid1 /dev/sdb /dev/sdc
>  mount /dev/sdb /mnt
>  # put data on /mnt
>  # then add /dev/sdd to the FS
>  btrfs-vol -a /dev/sdd /mnt
>
>  At this point we've got a raid1 filesystem with data spread across sdb and
>  sdc.  If we remove /dev/sdc, all the existing data will be remirrored onto
>  sdd:
>

Is there a way to check the progress of the remirror/rebuild ?
(somewhat similar to what /proc/mdstat provides when a mirror is being synced)



-- 
Miguel Sousa Filipe

  reply	other threads:[~2008-05-14 14:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13 20:08 Online device removal pushed to the unstable tree Chris Mason
2008-05-14 14:41 ` Miguel Sousa Filipe [this message]
2008-05-14 17:15   ` Chris Mason

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=f058a9c30805140741o7d4c4e67l243f981d1b750cca@mail.gmail.com \
    --to=miguel.filipe@gmail.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.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