From: Brian Rogers <brian@xyzw.org>
To: helmut@hullen.de
Cc: Helmut Hullen <Hullen@t-online.de>, linux-btrfs@vger.kernel.org
Subject: Re: 800 GByte free, but "no space left"
Date: Mon, 06 Dec 2010 01:56:31 -0800 [thread overview]
Message-ID: <4CFCB34F.1090504@xyzw.org> (raw)
In-Reply-To: <BbJPrrUD1uB@helmut.hullen.de>
On 12/05/2010 10:26 AM, Helmut Hullen wrote:
>> So, by far the simplest solution would be to re-create your file
>> system with "single" mode,
> Can I add or delete hard disks/partitions to the two devices/partitions
> in your example?
You can add, but you'll want to avoid deleting, balancing, and
shrinking. From my testing, any of these operations will convert the
chunks they relocate to raid0. Then, once you have any raid0 data, btrfs
will want to allocate all new chunks as raid0 and you'll have the
unusable space problem again.
> I've studied the man page and the Wiki but didn't find any help.
>
> And in my special case I have to add at least yearly new disks and from
> time to time remove the smallest disks from this bundle.
With the current state of btrfs, you could do this as long as you never
reduce the total number of disks. When you want to replace an old disk
with a new one, just go around btrfs: take the filesystem offline and
copy the old disk's partition into a full-sized partition on the new
disk. Then remove the old disk and bring the filesystem online again.
It will remember the old size at first, but that can be fixed with
btrfs filesystem resize <devid>:max <path>
Also, if you want metadata redundancy, you have to start your new
filesystem with two or more disks. Otherwise, the only way to change
metadata to raid1 is btrfs balance, which must be avoided.
Brian
next prev parent reply other threads:[~2010-12-06 9:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimJ3dDdOFiQb8G=rrjCk2h68Y59oWdKEGH-80jN@mail.gmail.com>
2010-12-05 7:48 ` 800 GByte free, but "no space left" Helmut Hullen
2010-12-05 8:59 ` cwillu
2010-12-05 9:51 ` Helmut Hullen
2010-12-05 10:36 ` cwillu
2010-12-05 11:46 ` Helmut Hullen
2010-12-05 11:08 ` Evert Vorster
2010-12-05 11:22 ` Hugo Mills
2010-12-05 12:21 ` Helmut Hullen
2010-12-05 13:49 ` Evert Vorster
2010-12-05 14:33 ` Helmut Hullen
2010-12-05 18:00 ` Evert Vorster
2010-12-05 18:26 ` Helmut Hullen
2010-12-06 9:56 ` Brian Rogers [this message]
2010-12-06 11:41 ` Hugo Mills
2010-12-05 20:28 ` Helmut Hullen
2010-12-06 7:43 ` Helmut Hullen
2010-12-06 11:43 ` Hugo Mills
2010-12-06 12:42 ` Helmut Hullen
2010-12-06 12:48 ` Hugo Mills
2010-12-06 13:13 ` Helmut Hullen
2010-12-06 13:28 ` Hugo Mills
2010-12-06 14:45 ` Helmut Hullen
2010-12-06 15:18 ` Hugo Mills
2010-12-06 17:13 ` Helmut Hullen
2010-12-06 18:29 ` Hugo Mills
2010-12-07 17:05 ` Helmut Hullen
2010-12-07 17:25 ` Hugo Mills
2010-12-07 17:44 ` Helmut Hullen
2010-12-05 11:35 ` Helmut Hullen
2010-12-02 18:23 Helmut Hullen
2010-12-03 3:28 ` Mike Fedyk
2010-12-03 6:47 ` Helmut Hullen
2010-12-04 17:17 ` Helmut Hullen
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=4CFCB34F.1090504@xyzw.org \
--to=brian@xyzw.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).