All of lore.kernel.org
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Or Tal <ortal99@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: No space on empty, degraded raid10
Date: Mon, 08 Sep 2014 07:01:14 -0400	[thread overview]
Message-ID: <540D8C7A.4030700@gmail.com> (raw)
In-Reply-To: <CAL-Saa_3uU936baHYjVOHXMVkNtP4mgLD6WuPUu2Wxw4SaPrzQ@mail.gmail.com>

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

On 2014-09-07 16:38, Or Tal wrote:
> Hi,
> 
> I've created a new raid10 array from 4, 4TB drives in order to migrate
> old data to it.
> As I didn't have enough sata ports, I:
> - disconnected one of the raid10 disks to free a sata port,
> - connected an old disk I wanted to migrate,
> - mounted the array with -o degraded
> - copied the data it it.
> 
> After about 2MB I got a "no space left on device message."
> btrfs fi df showed strange things - much less space in every category
> (about 8GB?) and none of then was full.
> 
> Ubuntu 14.10 beta - linux 3.16.0-14
Yeah, RAID10 doesn't really work in degraded mode (even if you have two
disks that have stripes from the same copy).  The approach that would be
needed for what you want to do is:
 1. Make a BTRFS RAID1 filesystem with _3_ new drives
 2. Connect one of the old disks
 3. Transfer data from old disk to new filesystem
 4. After repeating steps 2 and 3 for each old disk, connect the final
new disk, add it to the filesystem, and rebalance with '-dconvert=raid10
-mconvert=raid10'

Also, I've found out the hard way that system chunks really should be
RAID1, _NOT_ RAID10, otherwise it's very likely that the filesystem
won't mount at all if you lose 2 disks.


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2455 bytes --]

  reply	other threads:[~2014-09-08 11:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-07 20:38 No space on empty, degraded raid10 Or Tal
2014-09-08 11:01 ` Austin S Hemmelgarn [this message]
2014-09-11  6:40   ` Russell Coker
2014-09-11 11:19     ` Austin S Hemmelgarn
2014-09-11 11:38       ` Hugo Mills
2014-09-11 12:06         ` Austin S Hemmelgarn
2014-09-11 12:10           ` Hugo Mills

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=540D8C7A.4030700@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=ortal99@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.