From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: cloning single-device btrfs file system onto multi-device one
Date: 06 Apr 2011 08:30:00 +0200 [thread overview]
Message-ID: <BjKsrdvD1uB@helmut.hullen.de> (raw)
In-Reply-To: <BANLkTimQaPNm22kN8g2ha+XrOP3uyBUE-Q@mail.gmail.com>
Hallo, Evert,
Du meintest am 05.04.11:
>> I then did a btrfs fi balance again and let it run through. However
>> here is what I get:
>>
>> $ df -h /mnt
>> Filesystem =A0 =A0 =A0 =A0 =A0 =A0Size =A0Used Avail Use% Mounted on
>> /dev/sdb =A0 =A0 =A0 =A0 =A0 =A0 =A08.2T =A03.5T =A03.2T =A053% /mnt
>>
>> Only 3.2T left. How would I reclaim the missing space?
>>
>> $ sudo btrfs fi show
>> Label: none =A0uuid: ...
>> =A0 =A0 =A0 =A0Total devices 3 FS bytes used 3.43TB
>> =A0 =A0 =A0 =A0devid =A0 =A04 size 2.73TB used 1.17TB path /dev/sdc
>> =A0 =A0 =A0 =A0devid =A0 =A03 size 2.73TB used 1.17TB path /dev/sdb
>> =A0 =A0 =A0 =A0devid =A0 =A02 size 2.70TB used 1.14TB path /dev/sda4
>> $ sudo btrfs fi df /mnt
>> Data, RAID0: total=3D3.41TB, used=3D3.41TB
>> System, RAID1: total=3D16.00MB, used=3D232.00KB
>> Metadata, RAID1: total=3D35.25GB, used=3D20.55GB
>>
>> So that kind of worked but that is of little use to me as 2TB
>> kind of disappeared under my feet in the process.
> From my limited understanding, btrfs will write metadata in raid1 by
> default. So, this could be where your 2TB has gone.
> I am assuming you used raid0 for the three new disks?
No - take a look at the (shown) output of "btrfs fi df /mnt". "DATA" is=
RAID0.
Viele Gruesse!
Helmut
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-04-06 6:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 16:24 cloning single-device btrfs file system onto multi-device one Stephane Chazelas
2011-03-22 9:22 ` Stephane Chazelas
2011-03-23 0:06 ` cwillu
2011-03-28 13:17 ` Stephane Chazelas
2011-04-06 5:45 ` Evert Vorster
2011-04-06 6:30 ` Helmut Hullen [this message]
2011-04-06 6:57 ` Helmut Hullen
2011-04-06 8:25 ` Arne Jansen
2011-04-06 12:05 ` Stephane Chazelas
2011-04-06 13:43 ` Arne Jansen
2011-04-06 11:57 ` Stephane Chazelas
2011-03-23 5:13 ` Fajar A. Nugraha
2011-03-28 13:24 ` Stephane Chazelas
2011-03-30 11:58 ` Stephane Chazelas
2011-04-17 15:12 ` Hubert Kario
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=BjKsrdvD1uB@helmut.hullen.de \
--to=hullen@t-online.de \
--cc=helmut@hullen.de \
--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 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.