public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: regomodo <regomodo@googlemail.com>
To: Adrian von Bidder <avbidder@fortytwo.ch>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Mount via /etc/fstab constant failure
Date: Sat, 2 Jan 2010 12:26:01 +0000	[thread overview]
Message-ID: <201001021226.01754.regomodo@googlemail.com> (raw)
In-Reply-To: <201001011451.32725@fortytwo.ch>

On Friday 01 January 2010 13:51:26 Adrian von Bidder wrote:
> 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.
btrfs is compiled into my kernel. Should I make it a module instead?
> 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
> 

      reply	other threads:[~2010-01-02 12:26 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
2010-01-02 12:26       ` regomodo [this message]

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=201001021226.01754.regomodo@googlemail.com \
    --to=regomodo@googlemail.com \
    --cc=avbidder@fortytwo.ch \
    --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