From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: Adding a disk fails
Date: 21 Jan 2011 11:51:00 +0100 [thread overview]
Message-ID: <BeHcMpvT1uB@helmut.hullen.de> (raw)
In-Reply-To: <4D38B382.1050709@libero.it>
Hallo, Goffredo,
Du meintest am 20.01.11:
> To add another disk you don't have to run mkfs.btrfs. For example:
> # add the first disk
> mkfs.btrfs /dev/sdb
> # mount the disk
> mount /dev/sdb /media/backups
> # add another disk to the first one
> btrfs device add /dev/sdc /media/backup
> Note1: the filesystem has to be mounted
> Note2: the medatada will be in raid1, the data in raid0
Note 3: if the disk has been used (especially under btrfs) you should
first delete old partitioning data etc:
dd if=/dev/zero of=/dev/sdb count=1000
dd if=/dev/zero of=/dev/sdc count=1000
I've just tried your recipe with two devices I had used for other btrfs
experiments:
btrfs filesystem show 2>/dev/null
shows my new wishes, and it shows the old settings too.
But writing 1000 blocks seems to be not enough - sometimes I'll try
bigger numbers. What happens with the old (and now unwanted) settings?
By the way: I nee "2>/dev/null" because the actual git version always
tries to show all block devices which it finds in "/dev" (no: I don't
use "udev").
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2011-01-21 10:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 21:18 Adding a disk fails Carl Cook
2011-01-20 22:13 ` Goffredo Baroncelli
2011-01-20 23:10 ` Carl Cook
2011-01-21 6:55 ` Hubert Kario
2011-01-21 10:16 ` CACook
2011-01-21 10:41 ` Hubert Kario
2011-01-21 7:00 ` Helmut Hullen
2011-01-21 8:00 ` Fajar A. Nugraha
2011-01-21 18:42 ` Goffredo Baroncelli
2011-01-21 19:16 ` CACook
2011-01-21 6:57 ` Helmut Hullen
2011-01-21 10:51 ` Helmut Hullen [this message]
2011-01-21 13:23 ` Helmut Hullen
2011-01-20 22:31 ` Carl Cook
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=BeHcMpvT1uB@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 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).