linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: CACook@quantum-sci.com
To: linux-btrfs@vger.kernel.org
Subject: Re: Adding a disk fails
Date: Fri, 21 Jan 2011 02:16:49 -0800	[thread overview]
Message-ID: <201101210216.49389.CACook@quantum-sci.com> (raw)
In-Reply-To: <201101210755.54750.hka@qbs.com.pl>

On Thu 20 January 2011 22:55:54 Hubert Kario wrote:
> You still have a btrfs on /dev/sdc, do a 
> dd if=/dev/zero of=/dev/sdc bs=8192
> (overkill, but I don't remember which blocks have to be zeroed to destroy 
> btrfs superblock)

I gave up and started over.  Maybe it should be clarified in the wiki that no mkfs should be done on additional volumes, as it's counterintuitive to some.


> yes. rc.local is too late, unless you will also mount the volume from there 
> and not using /etc/fstab

How and when then?


> That depends - it has to be done before mounting. And if the device is
> part of the boot partition then you may put the "scan" command into an
> init-ramdisk.

This does not seem to have been sent to the listserv, as I only got it in a reply.  This is likely incomplete.


> Using something like "device=/dev/sdb,device=/dev/sdc" on fstab mount
> options should also work.

You mean as a substitute for a scan?

On my other server the btrfs array seems to mount just fine without any measures to scan.  I don't understand this,  nor why no specific advice is given about scanning on boot in the wiki.

  reply	other threads:[~2011-01-21 10:16 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 [this message]
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
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=201101210216.49389.CACook@quantum-sci.com \
    --to=cacook@quantum-sci.com \
    --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).