ext2resize
Quoted 6 lines · Stephen Tweedie
Hi,
Quoted 1 line · Andreas Dilger
I agree that reserving GDT blocks would be a small hack for v0 of ext2,
but
Quoted 1 line
Quoted 1 line
we could add a "COMPATIBLE" extension to v1 of ext2 that gave the number
of
Quoted 5 lines
Quoted 5 lines
GDT blocks reserved. Also, since the v1 sparse superblock filesystems leave a gap between the structures, there should not be a real problem. We just have to make sure that we agree (for example) that all the blocks from the start of the group to the block bitmap are reserved for the GDT. This is not a big strech, since this is already how v0 ext2 filesystems
are.
Quoted 4 lines
If you're going to be moving user data around anyway (and you have to be able to do this for the shrink case anyway), then relocating the inode/bitmap blocks is really not that much harder.
There's quite a difference between moving a non-metadata block and a metadata block. Non-metadata blocks are easily moved; they have only (max.) 1 reference somewhere. Moving metadata blocks is a bit harder, especially when the fs is mounted.
Moving the inode/block bitmap blocks is not that difficult when unmounted, but moving the inode table is tricky to get right (w.r.t atomicity). One ext2resize user got a segfault while the inode table was being moved (yes, that bug is fixed now) a while ago and we're still cleaning up the mess.
Lennert