From: Phillip Susi <psusi@cfl.rr.com>
To: Chuck Burns <break19@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: grub-1.99 and btrfs-only
Date: Mon, 07 Nov 2011 16:07:55 -0500 [thread overview]
Message-ID: <4EB848AB.1000006@cfl.rr.com> (raw)
In-Reply-To: <1485076.Kk29g2Lexo@funbeast>
On 11/5/2011 10:02 PM, Chuck Burns wrote:
> These are my current subvolumes:
> # btrfs sub list /
> ID 256 top level 5 path mainroot
> ID 257 top level 5 path home
>
> I have sub 256 set as default, and then home is mounted onto mainroot.
I advise against using set-default at all. The setup Ubuntu seems to be
going for ( and is working well for me so far ) creates two subvolumes
under the default root, named @ and @home, and intended to be mounted in
/ and /home respectively. The /@ subvolume is then mounted as the root
via rootflags=subvol=@ argument, and grub is configured to use
/@/boot/grub as its prefix directory.
I'm still getting a "sparse file not allowed" error during boot, and
have to press enter to continue though. Still not tracked that one down.
next prev parent reply other threads:[~2011-11-07 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 2:02 grub-1.99 and btrfs-only Chuck Burns
2011-11-07 21:07 ` Phillip Susi [this message]
2011-11-07 22:42 ` Arand Nash
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=4EB848AB.1000006@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=break19@gmail.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 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.