linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: C Anthony Risinger <anthony@extof.me>
To: Wenyi Liu <qingshenlwy@gmail.com>
Cc: david grant <dg@david-grant.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs problems and fedora 14
Date: Tue, 23 Nov 2010 00:45:02 -0600	[thread overview]
Message-ID: <AANLkTimkdtmjeO1Hzq5y1nL_ERNiJS1S0xn6Vu2_yyj=@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinuQU46BCL6WLM4hEc+ocXsbOGHoF3ppGbTOc8y@mail.gmail.com>

On Mon, Nov 22, 2010 at 10:47 PM, Wenyi Liu <qingshenlwy@gmail.com> wro=
te:
> 2010/11/23, david grant <dg@david-grant.com>:
>> I thought I would try btrfs on a new installation of f14. yes, I kno=
w
>> its experimental but stable so it seemed to be a good time to try it=
=2E
>> I am not sure if I have missed something out of all my searching but=
 am
>> I correct in thinking that currently:
>> =A0 =A0 =A0I. it is not possible to boot from a snapshot of the oper=
ating
>> =A0 =A0 =A0 =A0 system and, in particular, the yum snapshots cannot =
be used for
>> =A0 =A0 =A0 =A0 that purpose
>
> Is the Fedora grub support btrfs now?
> In this page http://fedoraproject.org/wiki/Features/SystemRollbackWit=
hBtrfs
> I got the following information:
> (deferred) a patch to grub1 -- on top of the already existing patch t=
o
> support btrfs in grub1 -- to allow selecting between snapshots of the
> boot partition.

all you need to do is add:

subvol=3D<name of the snapshot>

-- or --

subvolid=3D<id of the snapshot>

to your kernel boot line (edit in grub on the fly)... however, if
fedora is like archlinux in this respect (brief google search seems to
agree), you will actually need to add this:

rootflags=3Dsubvol=3D<name of the snapshot>

where `rootflags` are the mount options passed to the initramfs/root
device.  also, you reeeeally don't need grub, whatsoever[1]; in arch,
we use an initramfs hook to perform system rollback by dynamically
modifying the rootflags in accordance with the user's choice:

http://aur.archlinux.org/packages/mkinitcpio-btrfs/mkinitcpio-btrfs/btr=
fs_hook

perhaps someone in fedora can adapt that script... it's rather simple,
and it's MUCH easier and safer than fiddling with grub legacy[1].

C Anthony

[1] note however, that a proper grub2/extlinux solution is ideal to
support kernel-level rollbacks.  in the link above, everything is
rolled back except the kernel (residing on /boot... non-btrfs).
though, a kexec solution may be possible.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-11-23  6:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22 23:19 btrfs problems and fedora 14 david grant
2010-11-22 23:28 ` Hugo Mills
2010-11-23  4:47 ` Wenyi Liu
2010-11-23  6:45   ` C Anthony Risinger [this message]
2010-11-24  7:32     ` david grant
2010-11-24  9:19       ` cwillu
2010-11-26  9:40         ` david grant
2010-11-26 10:11           ` Oystein Viggen
2010-11-26 10:36             ` David Pottage
2010-11-26 17:47           ` cwillu

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='AANLkTimkdtmjeO1Hzq5y1nL_ERNiJS1S0xn6Vu2_yyj=@mail.gmail.com' \
    --to=anthony@extof.me \
    --cc=dg@david-grant.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=qingshenlwy@gmail.com \
    /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).