From: Goffredo Baroncelli <kreijack@libero.it>
To: Carl Cook <CACook@quantum-sci.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Adding a disk fails
Date: Fri, 21 Jan 2011 19:42:39 +0100 [thread overview]
Message-ID: <4D39D39F.5040806@libero.it> (raw)
In-Reply-To: <201101201510.54418.CACook@quantum-sci.com>
On 01/21/2011 12:10 AM, Carl Cook wrote:
> On Thu 20 January 2011 14:13:22 Goffredo Baroncelli wrote:
>> 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
>
> Thanks Goffredo but as I say, I did this and it responds with
> "ERROR: error adding the device '/dev/sdc'"
> .. it doesn't give a clue.
In your email you wrote that before adding the device you format it.
Anyway I don't think that this is the problem.
Have you check which is reported in dmesg.
>
>> Note1: the filesystem has to be mounted
>> Note2: the medatada will be in raid1, the data in raid0
>> If you shutdown the system, at the reboot you should "scan" all the
>> device in order to find the btrfs ones
>>
>> # find the btrfs device
>> btrfs device scan
>
> This must be done at every boot? If so, where is recommended, in rc.local?
Look at this thread, where I wrote anout a possible solution
http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg04709.html
>
>
>> # if you try to mount snapshot-3 directly, you fail because this
>> # snapshot is not under the root of the btrfs filesystem
>> mount -o subvol=dir-1/snapshot-3 /dev/sdb /media/backup # -> error
>
> This is how I'd understood it, but when creating a subvolume in the root and putting a snalshot into it, it seems to make a further subvolume (or directory) with a redundant name. This would not be under the root, and may not be mountable?
>
>
>> Which kenel version debian testing uses ?
>
> 2.6.32-5-amd64 with Debian patches.
>From a btrfs point of view, it is a very old kernel. IIRC in this kernel
is not supported the snapshot removal. I suggest you to update the
kernel with a recent one.
>
>
>> btrfs filesystem snapshot / /snapshot-$(date +"%Y-%m-%d")
>
> Oh thank you.
>
>
>
> --
> 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-01-21 18:42 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 [this message]
2011-01-21 19:16 ` CACook
2011-01-21 6:57 ` Helmut Hullen
2011-01-21 10:51 ` Helmut Hullen
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=4D39D39F.5040806@libero.it \
--to=kreijack@libero.it \
--cc=CACook@quantum-sci.com \
--cc=kreijack@inwind.it \
--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.