From: Felix Blanke <felixblanke@gmail.com>
To: helmut@hullen.de
Cc: Helmut Hullen <Hullen@t-online.de>, linux-btrfs@vger.kernel.org
Subject: Re: kernel 3.3.4 damages filesystem (?)
Date: Tue, 08 May 2012 20:41:47 +0200 [thread overview]
Message-ID: <4FA968EB.6050306@gmail.com> (raw)
In-Reply-To: <C8TGUFbuCXB@helmut.hullen.de>
On 5/8/12 8:29 PM, Helmut Hullen wrote:
> Hallo, Felix,
>
> Du meintest am 08.05.12:
>
>>> As I've written many times: I want a system for my video collection
>>> which allows
>>>
>>> adding a bigger disk
>>> deleting/removing a smaller disk
>>>
>>> with simple commands.
>>>
>>> btrfs seems to be able to do that (and I have tested this job many
>>> times). But with my configuration "mkfs.btrfs -m raid1 -d raid0"
>>> I've (again) seen that all data vanishes when 1 disk fails.
>>>
>>> I'll try Hugo's proposal "mkfs.btrfs -m raid1 -d single".
>>> And I hope that it doesn't make all disks unreadable when 1 disk
>>> fails.
>
> [...]
>
>> @"-d single"
>
>> Is it really possible to remove a disk from btrfs (created with -d
>> single) without losing the data on that disk?
>
> When the system is configured with
>
> mkfs.btrfs -m raid1 -d raid0
>
> then the above shown way is possible, it works (now) as expected.
> Ok - it needs some time.
>
> And I have yet told in this mailing list that I'll try the option 2-d
> single".
>
>> Is there a way to tell
>> balance to copy all the data from this disk to the other disks (ofc
>> if there is enough free space on them)?
>
> As I've written some hours ago: I run
>
> btrfs fi balance ...
>
> after adding and after deleting a disk. Maybe it's not necessary.
> Especially it seems not to be necessary after adding a disk.
What are the steps you're doing?! If this is really possible then there
must be some sort of command that tells btrfs "Hey, I wanne remove this
disk from the fs, please copy all data to the other disks and then
remove the disk". Is there such a command? Haven't heard of one, but
that would be interesting.
Otherwise if you remove a disk from a raid0 (doesn't matter if you have
2 or 5 or x disks in the fs, btrfs should stripe above all disks) your
fs should be broken.
>
> 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:[~2012-05-08 18:41 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 10:46 kernel 3.3.4 damages filesystem (?) Helmut Hullen
2012-05-07 10:58 ` Fajar A. Nugraha
2012-05-07 12:06 ` Helmut Hullen
2012-05-07 10:59 ` Hugo Mills
2012-05-07 12:15 ` Helmut Hullen
2012-05-07 13:34 ` Helmut Hullen
2012-05-07 14:05 ` Hugo Mills
2012-05-07 16:36 ` Helmut Hullen
2012-05-07 17:13 ` Felix Blanke
2012-05-07 17:52 ` Helmut Hullen
2012-05-07 18:00 ` Hugo Mills
2012-05-07 18:25 ` Helmut Hullen
2012-05-07 18:44 ` Hugo Mills
2012-05-09 13:04 ` failed disk (was: kernel 3.3.4 damages filesystem (?)) Helmut Hullen
2012-05-09 13:19 ` Hugo Mills
2012-05-09 14:25 ` Helmut Hullen
2012-05-09 14:37 ` Hugo Mills
2012-05-09 15:14 ` failed disk Helmut Hullen
2012-05-09 15:33 ` Hugo Mills
2012-05-09 18:49 ` Helmut Hullen
2012-05-09 16:13 ` failed disk (was: kernel 3.3.4 damages filesystem (?)) Ilya Dryomov
2012-05-10 2:49 ` failed disk Helmut Hullen
2012-05-07 19:30 ` kernel 3.3.4 damages filesystem (?) Daniel Lee
2012-05-07 20:21 ` Helmut Hullen
2012-05-07 20:51 ` Daniel Lee
2012-05-07 21:17 ` Helmut Hullen
2012-05-07 21:27 ` cwillu
2012-05-07 22:07 ` Martin Steigerwald
2012-05-08 7:39 ` Helmut Hullen
2012-05-08 7:44 ` Fajar A. Nugraha
2012-05-08 10:00 ` Helmut Hullen
2012-05-08 10:41 ` Clemens Eisserer
2012-05-08 13:13 ` Helmut Hullen
2012-05-08 13:44 ` Felix Blanke
2012-05-08 13:52 ` Hugo Mills
2012-05-08 16:53 ` Helmut Hullen
2012-05-08 17:24 ` Felix Blanke
2012-05-08 18:29 ` Helmut Hullen
2012-05-08 18:41 ` Felix Blanke [this message]
2012-05-08 19:12 ` David Sterba
2012-05-08 19:34 ` Helmut Hullen
2012-05-08 20:02 ` Hugo Mills
2012-05-08 20:19 ` Helmut Hullen
2012-05-08 20:56 ` Roman Mamedov
2012-05-09 14:46 ` Kaspar Schleiser
2012-05-10 10:40 ` Martin Steigerwald
2012-05-10 11:55 ` feature request (was: kernel 3.3.4 damages filesystem (?)) Helmut Hullen
2012-05-10 19:43 ` kernel 3.3.4 damages filesystem (?) Hubert Kario
2012-05-10 20:15 ` Hugo Mills
2012-05-10 20:23 ` Hubert Kario
2012-05-08 21:42 ` Hubert Kario
2012-05-07 12:53 ` Liu Bo
2012-05-09 17:32 ` Duncan
2012-05-09 18:06 ` Atila
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=4FA968EB.6050306@gmail.com \
--to=felixblanke@gmail.com \
--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 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.