From: Mike Field <mafield@the.net.nz>
To: linux-lvm@msede.com
Subject: [linux-lvm] Alpha testers rqd for ext2 fs extend utility.
Date: Mon, 28 Jun 1999 20:32:54 +1200 [thread overview]
Message-ID: <37773336.2DFD841C@the.net.nz> (raw)
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????
next reply other threads:[~1999-06-28 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-28 8:32 Mike Field [this message]
1999-06-28 20:32 ` [linux-lvm] Alpha testers rqd for ext2 fs extend utility Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
1999-06-29 7:49 Peter Wuestefeld
1999-06-29 22:53 ` Andreas Dilger
1999-06-30 5:00 ` guruju
1999-06-30 4:35 ` Andreas Dilger
1999-06-30 17:42 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37773336.2DFD841C@the.net.nz \
--to=mafield@the.net.nz \
--cc=linux-lvm@msede.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.