From: Anand Jain <anand.jain@oracle.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
Qu Wenruo <quwenruo@cn.fujitsu.com>,
linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz, calestyo@scientia.net, ahferroin7@gmail.com,
1i5t5.duncan@cox.net
Subject: Re: [PATCH 0/7] Let user specify the kernel version for features
Date: Mon, 30 Nov 2015 12:54:19 +0800 [thread overview]
Message-ID: <565BD67B.9090007@oracle.com> (raw)
In-Reply-To: <565A5317.8040506@gmx.com>
(Most of the technical reasoning were already discussed so I won't
repeat them here).
And jolting for new technical reasons finds only these..
> What if the fs is not only for kernel to mount, but also a boot
> partition for grub?
> Do you need to check the grub2 version? Check if this is a /boot partition?
In the above context, which is better..
this :
mkfs.btrfs -O ^skinny-metadata,^mixed-bg,^extref,^raid56,^no-holes
btrfs-convert -O ^skinny-metadata,^extref,^no-holes
or this:
mkfs.btrfs -O comp=<X>
btrfs-convert -O comp=<X>
X = some number below 2.7.37 OR grub2 (planned) (thanks to you,
to bring this up).
?
> Recently I just encountered such problem. Latest xfs-progs makes xfs
> version 5 by default, but grub2 can't handle version 5 yet in latest
> stable version.
> Then system can't even boot into grub2.
Good example. Appears that user didn't know what latest features
to disable? so to be compatible with grub2 ? OR they have to read
couple of grub documents to fix.
Imagine the pain while using btrfs-convert. That means you need to
restore Hope you have not deleted the ext_saved subvol. And then
again run btrfs-convert.
> Did you see Dave trying to add such grub2 version based probe to change
> mkfs.xfs features?
> No, just because that's not the way things should be done.
So what was fix in this case ? Or is there any fix-patch rejected ?
Cheers, Anand
next prev parent reply other threads:[~2015-11-30 4:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 12:08 [PATCH 0/7] Let user specify the kernel version for features Anand Jain
2015-11-25 12:08 ` [PATCH 1/7] btrfs-progs: show the version for -O list-all Anand Jain
2015-11-25 12:08 ` [PATCH 2/7] btrfs-progs: add kernel alias for each of the features in the list Anand Jain
2015-11-25 13:36 ` [PATCH V1.1 " Anand Jain
2015-11-25 18:11 ` [PATCH " Liu Bo
2015-11-25 22:52 ` Anand Jain
2015-11-25 12:08 ` [PATCH 3/7] btrfs-progs: make is_numerical non static Anand Jain
2015-11-25 12:08 ` [PATCH 4/7] btrfs-progs: check for numerical in version_to_code() Anand Jain
2015-11-25 12:08 ` [PATCH 5/7] btrfs-progs: introduce framework version to features Anand Jain
2015-11-25 12:08 ` [PATCH 6/7] btrfs-progs: add -O comp= option for mkfs.btrfs Anand Jain
2015-11-25 12:08 ` [PATCH 7/7] btrfs-progs: add -O comp= option for btrfs-convert Anand Jain
2015-11-26 2:02 ` [PATCH 0/7] Let user specify the kernel version for features Qu Wenruo
2015-11-26 6:07 ` Anand Jain
2015-11-26 6:53 ` Qu Wenruo
2015-11-26 11:18 ` Anand Jain
2015-11-26 12:31 ` Qu Wenruo
2015-11-26 22:17 ` Anand Jain
2015-11-27 0:44 ` Qu Wenruo
2015-11-27 8:41 ` Anand Jain
2015-11-29 1:21 ` Qu Wenruo
2015-11-30 4:54 ` Anand Jain [this message]
2015-11-30 5:46 ` Qu Wenruo
2016-02-03 10:50 ` David Sterba
2016-02-04 1:12 ` Qu Wenruo
2016-02-04 1:42 ` Chris Mason
2015-11-30 5:44 ` potential btrfs-progs clean up Anand Jain
2015-11-30 6:12 ` Qu Wenruo
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=565BD67B.9090007@oracle.com \
--to=anand.jain@oracle.com \
--cc=1i5t5.duncan@cox.net \
--cc=ahferroin7@gmail.com \
--cc=calestyo@scientia.net \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=quwenruo@cn.fujitsu.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).