All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian von Bidder <avbidder@fortytwo.ch>
To: linux-btrfs@vger.kernel.org
Cc: regomodo <regomodo@googlemail.com>
Subject: Re: Mount via /etc/fstab constant failure
Date: Fri, 1 Jan 2010 14:51:26 +0100	[thread overview]
Message-ID: <201001011451.32725@fortytwo.ch> (raw)
In-Reply-To: <200912312044.58341.regomodo@googlemail.com>

[-- Attachment #1: Type: Text/Plain, Size: 1149 bytes --]

On Thursday 31 December 2009 21.44:58 regomodo wrote:
> On Thursday 31 December 2009 19:24:12 Chris Ball wrote:
> > Hi Reg,
> >
> >    > Hi, I have a btrfs 'pool' of x2 Samsung 500GB HDD's in non-raid
> >    > format. It works fine for the most part except for mounting on
> >    > bootup. Every bootup I have to change the block-device to and fro
> >    > /dev/sda & /dev/sdb. This happens on linux-2.6.32.2 and
> >    > 2.6.33-rc2.
> >
> > Are you running "btrfsctl -a" in an initrd?  It's necessary to do that
> > before the mount call on a multi-disk volume.
> 
> I did not know that. I've just given it a try on Funtoo and Ubuntu and it
> makes no difference. On Funtoo, my small script runs 'btrfsctl -a' at the
>  boot runlevel but I still get those 3 errors. I even try running
>  'btrfsctl -a' again before I try 'mount -av' but still no luck.

I had a similar issue and discovered that "btrfsctl -a" doesn't load the 
btrfs module.  So I do "modprobe btrfs; btrfsctl -a"

cheers
-- vbi


-- 
The idea is that you can only get in trouble for what you actually did.
What a concept.
        -- Pam Jones, Groklaw

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 389 bytes --]

  reply	other threads:[~2010-01-01 13:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-31 18:22 Mount via /etc/fstab constant failure regomodo
2009-12-31 19:24 ` Chris Ball
2009-12-31 20:44   ` regomodo
2010-01-01 13:51     ` Adrian von Bidder [this message]
2010-01-02 12:26       ` regomodo

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=201001011451.32725@fortytwo.ch \
    --to=avbidder@fortytwo.ch \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=regomodo@googlemail.com \
    /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.