From: "Javier Martín" <lordhabbit@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub-probe detects ext4 wronly as ext2
Date: Wed, 16 Jul 2008 18:38:09 +0200 [thread overview]
Message-ID: <1216226289.13612.38.camel@localhost> (raw)
In-Reply-To: <C1915CE4533B47129A352F88C937B29F@fz>
[-- Attachment #1: Type: text/plain, Size: 2532 bytes --]
El mié, 16-07-2008 a las 17:27 +0200, Felix Zielcke escribió:
> From: "JavierMartín" <lordhabbit@gmail.com>
> Sent: Wednesday, July 16, 2008 5:09 PM
> To: "The development of GRUB 2" <grub-devel@gnu.org>
> Subject: Re: grub-probe detects ext4 wronly as ext2
>
> > I see the ext4 patch was checked in recently. Can the "forbid-incompat"
> > patch with the new, specific error messages be committed too then? I'm
> > submitting an updated version (i.e. against the current HEAD) because
> > new lines were added.
> >
> > PS: does the ext4 patch add support for META_BG? it should be added to
> > the list of supported incompat features then.
>
> I don't know what this META_BG is but even the ext2 kernel driver supports
> it [0]
Er... of course, the Linux extN implementation is the de-facto reference
implementation. Some incompat features are only used in newer versions
like ext3 and ext4, while others are added to ext2 too. I was talking
about the GRUB extN driver, which recently got patched by Bean.
> Maybe the list of flags have a bit changed so I'm so nice and give you even
> a git link to the current ext4.h in Linus' official git tree [1]
> You'll probably mean FLEX_BG :)
All those flags make my head spin so fast I'll create a dark hole
through gravitomagnetic effects. I no longer know what the hell does
each one do T_T
>
> I didn't take a deep look at the changes between the first patch from Bean
> and the last one which he commited.
> But for me it's now working fine with whole / on ext4 made with the final
> e2fsprogs 1.41 in Debian unstable,
> with flex_bg,extents and uninit_bg from the INCOMPAT list, so flex_bg and
> uninit_bg should be added to your list which are ignored/supported
Uninit_bg is signaled (iIrc) in the superblock by a ROCOMPAT flag,
GDT_CSUM, and then in the block groups by whatever-it-is (head spinning
even faster).
>
> Maybe it's just luck for me that it works now with uninit_bg and flex_bg,
> the best would be if other people would test it
AFAIK, uninit_bg should work if the (readonly) GRUB reader respects the
spec and skips "invalid" block groups/inodes/whatever (those that
haven't been initialized). As I don't know what the f*** do META_BG and
FLEX_BG do, I can't tell you whether they truly work or it's just a
matter of luck: it's Bean who can tell us whether or not he implemented
support for them - I only added the "extents" flag to the supported list
on my patch, but including more is a matter of seconds.
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2008-07-16 16:38 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 18:11 grub-probe detects ext4 wronly as ext2 Felix Zielcke
2008-06-29 18:46 ` Javier Martín
2008-06-29 19:17 ` Bean
2008-06-29 19:53 ` Javier Martín
2008-06-29 21:19 ` Robert Millan
2008-06-30 3:02 ` Javier Martín
2008-06-30 7:10 ` Felix Zielcke
2008-06-30 11:14 ` Isaac Dupree
2008-06-30 12:12 ` Javier Martín
2008-06-30 12:27 ` Bean
2008-06-30 12:43 ` Javier Martín
2008-07-01 16:08 ` Robert Millan
2008-07-01 16:25 ` Pavel Roskin
2008-07-01 18:42 ` Javier Martín
2008-07-01 19:01 ` Pavel Roskin
2008-07-01 20:48 ` Robert Millan
2008-07-01 23:05 ` Javier Martín
2008-07-01 23:28 ` Javier Martín
2008-07-02 14:22 ` Robert Millan
2008-07-02 16:03 ` Pavel Roskin
2008-07-02 19:32 ` Javier Martín
2008-07-03 14:02 ` Robert Millan
2008-07-03 14:21 ` Isaac Dupree
2008-07-03 17:07 ` Javier Martín
2008-07-04 0:08 ` Robert Millan
2008-07-04 1:20 ` Javier Martín
2008-08-05 17:23 ` Felix Zielcke
2008-08-06 10:36 ` Felix Zielcke
2008-08-11 0:35 ` Javier Martín
2008-08-11 7:56 ` Felix Zielcke
2008-07-04 1:32 ` Javier Martín
2008-07-04 6:49 ` Bean
2008-07-04 8:33 ` Felix Zielcke
2008-07-04 10:34 ` Javier Martín
2008-07-04 11:29 ` Bean
2008-07-04 12:00 ` Javier Martín
2008-07-04 14:09 ` Robert Millan
2008-07-04 14:33 ` Javier Martín
2008-07-04 14:11 ` Bean
2008-07-04 14:34 ` Javier Martín
2008-07-04 14:04 ` Robert Millan
2008-07-04 14:23 ` Robert Millan
2008-07-04 14:21 ` Robert Millan
2008-07-04 14:45 ` Javier Martín
2008-07-04 18:57 ` Robert Millan
2008-07-04 20:41 ` Javier Martín
2008-07-05 12:07 ` Robert Millan
2008-07-05 18:36 ` Javier Martín
2008-07-16 15:09 ` Javier Martín
2008-07-16 15:27 ` Felix Zielcke
2008-07-16 16:38 ` Javier Martín [this message]
2008-07-16 17:13 ` Felix Zielcke
2008-07-16 17:21 ` Felix Zielcke
2008-07-16 17:44 ` Felix Zielcke
2008-07-16 19:07 ` Javier Martín
2008-07-16 19:33 ` Felix Zielcke
2008-07-19 14:27 ` Robert Millan
2008-08-11 14:14 ` Javier Martín
2008-08-27 13:58 ` Felix Zielcke
2008-08-30 11:17 ` Robert Millan
2008-08-30 21:28 ` Javier Martín
2008-09-24 17:05 ` Javier Martín
2009-02-04 7:41 ` Felix Zielcke
2009-02-04 13:08 ` Javier Martín
2009-02-07 19:30 ` Felix Zielcke
2009-02-07 23:54 ` Javier Martín
2009-02-08 0:28 ` Robert Millan
2008-07-01 16:03 ` Robert Millan
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=1216226289.13612.38.camel@localhost \
--to=lordhabbit@gmail.com \
--cc=grub-devel@gnu.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