From: Russell Coker <russell@coker.com.au>
To: george@chinilu.com
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Scan not being performed properly on boot
Date: Mon, 04 Aug 2014 15:01:53 +1000 [thread overview]
Message-ID: <3123040.QXoTpzZbhi@xev> (raw)
In-Reply-To: <53DF0D55.3050504@chinilu.com>
On Sun, 3 Aug 2014 21:34:29 George Mitchell wrote:
> I see what you are saying. Its a hack. But I suspect that most of the
> distros are not yet accommodating btrfs with their standard mkinitrd
> process. At this point modifying grub2 config does solve the problem.
> If you know a reasonably easy way to fix initrd so that it can interpret
> UUID and LABEL, I would certainly be all ears.
Debian/Wheezy works with BTRFS when using UUID= to specify the root
filesystem. Wheezy was released in May 2013, Ubuntu 14.04 was released in
April 2014 and as Ubuntu is based on Debian it should have at least the same
features as an older version of Debian.
I think that most Distributions are supporting BTRFS. Debian/Wheezy has
support for BTRFS (although I recommend that you don't use it unless you plan
to take a kernel from Testing), most Debian derivatives will support it,
Fedora supports it.
It's probably better to make a list of distributions that DON'T support BTRFS,
it'll be a shorter list.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2014-08-04 5:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 3:02 Scan not being performed properly on boot Peter Roberts
2014-08-04 3:31 ` Russell Coker
2014-08-04 4:00 ` George Mitchell
2014-08-04 4:14 ` Russell Coker
2014-08-04 4:22 ` George Mitchell
2014-08-04 4:34 ` George Mitchell
2014-08-04 5:01 ` Russell Coker [this message]
2014-08-04 5:23 ` Duncan
2014-08-04 9:36 ` Chris Samuel
2014-08-04 15:00 ` Peter Roberts
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=3123040.QXoTpzZbhi@xev \
--to=russell@coker.com.au \
--cc=george@chinilu.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).