Alpha testers rqd for ext2 fs extend utility.
I'm a HP-UX user and love LVM. I find the lack of an free extendfs utility a real hole in LVM on Linux - so I've done something about it!
I've finially hacked togeather to version 0.1.0 of ext2end - my ext2 file system extend utlity. It has two limitations at present:
1. It cannot extend a file further than the limit of the group descriptor table (in practice over 256M boundary for 1024 byte blocks). So a 257Mb file system can be extended to a 512 MB file system, but a 255M Bone can't be extended to 257MB. This will be fixed as soon as I learn enough about inodes to do some inode relocation, allowing the group descriptor table to be extended without moving all the data.
2. Because I am using lseek() the maximum file system size that I would be confident running it on is 2GB (but it might run upto 4GB... maybe). If anybody knows how to do block oriented file IO under linux can they drop me a email. Otherwise I'll have to troll the glib sources...
A minor issue is that the number of nodes is fixed to the number of inodes/per group as the original file system (to avoid moving data around): if you need more Inodes you have to extend a lot - maybe upto 8MB to open a new group...
Apart from that it works, but it is early, early alpha. I'm looking for some alpha testers to send my source tarballs to. Please don't sign up unless you have a tape drive :-)
Also, don't expect too much - command line options (like disabling the pre/post-extend fscks) and header comments in source files are on the list for for version 0.1.1, and debuging switches are changed in a source file (for 0.1.1 also). Hell, it might even allow you to attempt to extend mounted file systems (can you say 'kernel panic'?). This project will officially put under the GPL, but at the moment I'ld rather fix limitations 1&2 that worry about paperwork.
So till version 0.2.0, if you want it, send a mail, I'll send you the source.
Mike Field
PS. Anybody got any spare web space to host the source????
Quoted 2 lines · Mike Field
I'm a HP-UX user and love LVM. I find the lack of an free extendfs utility a real hole in LVM on Linux - so I've done something about it!
Just in case you hadn't seen the discussion lately here and on linux-fsdevel mailing list, Lennert Buytenhek is also working on a GPL ext2 extender. It apparently will handle the 256MB limit by moving data blocks around during the resize as well. I don't have the URL handy, but it was posted in the linux-lvm mailing list in the last week.
One thing I was thinking is if we can't make the ext2 resize work past the 256MB boundary while the filesystem is mounted, we could have the existing "ext2-resize" program do the resizing while unmounted, but also have a different utility (or a separate function of ext2-resize) that will allow growth to the next 256MB boundary while the FS is mounted, for those emergency times when you just need a bit more space and can't afford a shutdown...
Another possibility (if the ext2 kernel code can handle it) is to build the ext2 filesystem "pre-enlarged" with enough group descriptors and inode blocks for a much larger filesystem, and then we don't have the issue of moving blocks around on a (un)mounted filesystem. I think that this is what AIX does, since when you create a new JFS filesystem (selecting bytes/inode and cluster size) it replies with:
Based on the parameters chosen, the new /tt JFS file system is limited to a maximum size of 134217728 (512 byte blocks)
so there is a pre-determined JFS size limit as well, it's just a very large one. That would be the equivalent of ext2's 256MB resize limit, and AIX JFS doesn't allow you to expand past the size which is determined at JFS creation time.
I know that there are calculations in the kernel, and in the ext2 tools which work out GD size and inode block counts based on the total number of blocks, but would it be possible to somehow dissociate these two numbers, and say we will have X group descriptors, and Y inode blocks no matter how big the FS currently is? Then all we have to do is pick X and Y large enough to satisfy most expansion limits, maybe 128x as large as the original filesystem size.
Cheers, Andreas
Signature · 4 lines
Andreas Dilger University of Calgary \"If a man ate a pound of pasta and
Micronet Research Group \ a pound of antipasto, would they
Dept of Electrical & Computer Engineering \ cancel out, leaving him still
http://www-mddsp.enel.ucalgary.ca/People/adilger/ hungry?" -- Dogbert