All of lore.kernel.org
 help / color / mirror / Atom feed
From: dima <dolenin@parallels.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Snapshot rollback
Date: Mon, 24 Oct 2011 08:24:38 +0000 (UTC)	[thread overview]
Message-ID: <loom.20111024T101858-236@post.gmane.org> (raw)
In-Reply-To: CAG1y0sfmnD8W7an-7HicwfH0HuzJA4wnOLq90qn5iTJmEs4v0w@mail.gmail.com

Fajar A. Nugraha <list <at> fajar.net> writes:
 
> A problem with that, though, if you decide to put /boot on btrfs as
> well. Grub uses the default subvolume to determine paths (for kernel,
> initrd, etc). A workaround is to manually create and manage your
> grub.cfg (or create and use a manual-managed include file, like
> custom-top.cfg, that gets parsed before the automatically created
> entries).

Oops, sorry, I was incorrect of course. Thanks Fajar.
I do have /boot in my subvolid=0 because bootloaders can't read inside
subvolumes (other than the default) as far as I understand.
And I just bind /boot through fstab.


  reply	other threads:[~2011-10-24  8:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-23 19:42 Snapshot rollback Phillip Susi
2011-10-23 20:35 ` Goffredo Baroncelli
2011-10-24  5:45 ` dima
2011-10-24  5:58   ` Fajar A. Nugraha
2011-10-24  8:24     ` dima [this message]
2011-10-24 12:11       ` Fajar A. Nugraha
2011-10-25  2:00         ` dima
2011-10-25  8:01           ` Fajar A. Nugraha
2011-10-25  8:54             ` dima
2011-10-25  9:01               ` Fajar A. Nugraha
2011-10-25  0:45   ` Phillip Susi
2011-10-25  2:04     ` Arand Nash
2011-10-26  1:30       ` Phillip Susi
  -- strict thread matches above, loose matches on Subject: below --
2019-07-05 10:38 snapshot rollback Ulli Horlacher
2019-07-05 11:06 ` Ulli Horlacher
2019-07-05 11:47   ` Remi Gauvin
2019-07-05 13:03     ` Graham Cobb
2019-07-05 21:18 ` Chris Murphy

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=loom.20111024T101858-236@post.gmane.org \
    --to=dolenin@parallels.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.