Re: [PATCH] ext4 extent support

["Javier Martín" <lordhabbit@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]

El sáb, 05-07-2008 a las 19:15 +0200, Felix Zielcke escribió:
> From: "JavierMartín" <lordhabbit@gmail.com>
> Sent: Saturday, July 05, 2008 3:25 PM
> To: "The development of GRUB 2" <grub-devel@gnu.org>
> Subject: Re: [PATCH] ext4 extent support
> 
> >I think flex_bg support is unimplemented right now (at least I didn't
> >see it anywhere), but it "worked" because it's not being used? Just a
> >guess
> 
> I just checked.
> Kernel 2.6.26-rc8 has a bit code with flex_bg
> e2fsprogs 1.41WIP from Debian experimantel has a bit more code with flex 
> (not much with flex_bg more flexbg or just _flex)
> But I don't know much C so I don't understand the code :)
> Anyway I think the most important ext4 support are extents, because you can 
> enable them by just remounting to ext4 as long as you don't use noextents 
> mount option
> flex_bg can only be enabled by mkfs.ext4(dev) not afterwards with tune2fs 
> but it's default enabled in mke2fs.conf for ext4(dev)
> uninit_bg isn't enabled by default and can be enabled afterwards with 
> tune2fs but resize2fs isn't currently working with it 
I mean unimplemented in GRUB right now. IIrc, flex_bg relaxes some of
the rules governing the location of the metadata block groups or
something like that, so that they can be placed in "arbitrary"
locations.
Uninit_bg allows yet-unused block groups and inode tables to be
initalized on first use, and saves a lot of time in mkfs (because it
doesn't have to write all the inode tables) and fsck (because there's no
need to check unused block groups at all).


[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 827 bytes --]