On Tue, Jan 29, 2008 at 06:24:09PM +0100, Stefan Lippers-Hollmann wrote:
>
> ext3 filesystems with an inode size of 256 byte cannot be read by the
> read-only file system code of debian's/ upstream's grub 0.97 (e2fs_stage1_5
> can't be loaded). Given that e2fsprogs 1.40.5-1 has started to use 256 byte
> inodes on default, creating new filesystems without explicitly decreasing
> the inode size creates filesystems which aren't bootable by current grub
> versions.
It is highly desirable that new filesystems use 256 byte inodes, since
it provides for better forward compatibility with ext4, and it speeds
up extended attribute storage for systems that use SELinux and/or Samba4.
If the grub maintainers can't figure out a way to break up the
monolithic patch quickly, or to get it incorporated into Debian, or
get it upstreamed ASAP, one of the things that I could do is change
mke2fs.conf in the udeb file, so that it doesn't impact the Debian
installer. Or better yet, the Anaconda could be hacked so that "-I
128" is passed to mke2fs just for the root filesystem, and not for
others.
But it really would be DoublePlusCool if we could get the 256 byte
inode support into Grub quickly, so we don't need to pursue these
workarounds. If the grub folks could let me know what they think can
be pulled off, I would really appreciate it.
Thanks!!!!
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
