From: dima <dolenin@parallels.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Snapshot rollback
Date: Tue, 25 Oct 2011 02:00:43 +0000 (UTC) [thread overview]
Message-ID: <loom.20111025T034412-244@post.gmane.org> (raw)
In-Reply-To: CAG1y0sc_2+NZm0o8Ng_kyjWgZLZZ3SaJ3=5-0SG2_4r1tKjwoQ@mail.gmail.com
Fajar A. Nugraha <list <at> fajar.net> writes:
> AFAIK you have three possible ways to use /boot on btrfs:
>
> (1) put /boot on subvolid=0, don't change the default subvolume. That
> works, but all your snapshot/subvols will be visible under /boot. Some
> people might not want that for estetic reason.
Hi Fajar,
I think I am doing just this, but my subvolumes are not visible under /boot. I
have all my subvolumes set up like this:
/path/to/subvolid_0/boot < a simple directory bind-mounted to /
/path/to/subvolid_0/__active < my / subvolume
/path/to/subvolid_0/__home < my /home subvolume
> (3) put /boot on a subvolume, do not change the default subvolume, and
> manage grub.cfg manually. This is what I currently do.
Could you elaborate about this option pls., and if possible post your grub.cfg?
I don't quite understand how it works. Though I am doing syslinux at the moment,
I think the process is the same.
thanks
~dima
next prev parent reply other threads:[~2011-10-25 2:00 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
2011-10-24 12:11 ` Fajar A. Nugraha
2011-10-25 2:00 ` dima [this message]
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.20111025T034412-244@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox