On Tue, Apr 15, 2008 at 11:52:16AM -0500, Jose R. Santos wrote:
> As discuss on the call yesterday, some folks (my self included) really
> want a TODO list to help them keep track of what things are left undone
> in e2fsprogs as we try to get ext4 out the door. Here is my initial
> list of items that still need addressing. Hopefully we can expand this
> list and document it somewhere like the ext4 wiki or the SourceForge
> bug tracker.
>
> - Rename uninit_groups to uninit_bg to be consistent with other
> defined features. Retain the old name for historical purpose.
Yes. Although until we actually don't do lazy initialization of the
inode table, I still think the name is a bit of a misnomer. It really
is more about checksuming the block group descriptors and a faster
fsck, but whether or not we initialize the block groups or not is
pretty much a non-issue.
> - The return value of ext2fs_super_and_bgd_loc() is not to be trusted.
> Document this in the source code.
>
> - Make sure ext2fs_super_and_bgd_loc() does not get used anywhere where
> the return value is expected to be accurate (aside from mke2fs).
>
> - Remove lazy_bg feature from being set in mke2fs. Feature has been
> declare a dangerous hack by its creator, remove it to avoid people
> building on top of it.
.... and to replace it, add a configuration parameter to
/etc/e2fsck.conf which controls whether or not the inode table and
bitmap blocks should be uninitialized when using uninit groups. It
will default to off for now, until the kernel support can be
implemented.
> - Add flex_bg meta-data grouping support.
Once it is demonstrated to work correctly in all circumstances. :-)
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
