From: C Anthony Risinger <anthony@extof.me>
To: Josef Bacik <josef@redhat.com>
Cc: Mitch Harder <mitch.harder@sabayonlinux.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: add support for mixed data+metadata block groups V3
Date: Thu, 21 Oct 2010 21:06:38 -0500 [thread overview]
Message-ID: <AANLkTikwEDcR41QBPT6maf0pv_4knQDifFkrx4kq3_Bm@mail.gmail.com> (raw)
In-Reply-To: <20101022013701.GH30906@dhcp231-156.rdu.redhat.com>
On Thu, Oct 21, 2010 at 8:37 PM, Josef Bacik <josef@redhat.com> wrote:
> On Thu, Oct 21, 2010 at 08:32:12PM -0500, C Anthony Risinger wrote:
>> On Thu, Oct 21, 2010 at 8:05 PM, Josef Bacik <josef@redhat.com> wrot=
e:
>> > On Thu, Oct 21, 2010 at 05:21:06PM -0500, Mitch Harder wrote:
>> >> On Thu, Oct 21, 2010 at 5:09 PM, Diego Calleja <diegocg@gmail.com=
> wrote:
>> >> > On Jueves, 21 de Octubre de 2010 17:46:58 David Nicol escribi=F3=
:
>> >> >> Does this mixing constitute a forbidden change of on-disk form=
at, and
>> >> >> if not how not?
>> >> >
>> >> > It doesn't need a format change. The difference between a data =
and
>> >> > a metadata block group is just an allocation hint AFAIK.
>> >> > --
>> >> > 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 =A0http://vger.kernel.org/majordomo-info=
=2Ehtml
>> >> >
>> >>
>> >> Let me know if the problems with an un-patched kernel were un-exp=
ected.
>> >>
>> >> I can provide more information on the crash when booting an older=
kernel.
>> >
>> > Nope they are expected, it's not a disk format change, but older k=
ernels won't
>> > deal with mixed block groups.
>>
>> When something like this goes mainline, is it used by default/automa=
tically?
>>
>> I ask because I maintain a btrfs-based rollback initramfs hook [1],
>> and am currently updating it for extlinux, enabling kernel-level
>> system rollbacks via `btrfs set-default` + reboot (or maybe
>> `kexec`)...
>>
>> rolling back to an old kernel will then blow up my machine
>> (figuratively of course :-)?
>>
>
> The only way you get this feature is if you mkfs with the feature ena=
bled, and
> is only meant for small filesystems (1 gig or smaller).
Ah right :-), thanks
C Anthony
--
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
prev parent reply other threads:[~2010-10-22 2:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 11:51 [PATCH] Btrfs: add support for mixed data+metadata block groups V3 Josef Bacik
2010-10-21 4:21 ` Mitch Harder
2010-10-21 15:46 ` David Nicol
2010-10-21 22:09 ` Diego Calleja
2010-10-21 22:21 ` Mitch Harder
2010-10-22 1:05 ` Josef Bacik
2010-10-22 1:32 ` C Anthony Risinger
2010-10-22 1:37 ` Josef Bacik
2010-10-22 2:06 ` C Anthony Risinger [this message]
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=AANLkTikwEDcR41QBPT6maf0pv_4knQDifFkrx4kq3_Bm@mail.gmail.com \
--to=anthony@extof.me \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mitch.harder@sabayonlinux.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).