Mailing List Archive

determining the minimum safe size for resizing ext2/3
I have been googling for a few days trying to figure out the answer to this
question. Parted is capable of determining this value and performing the resize
itself, but only with ext2/3 filesystems created with older version of mke2fs
(part of e2fsprogs).

Instead of using libext2 provided with e2fsprogs, the author of parted decided
to fork the e2fsprogs code back in ~2001. Because of this, the resize2fs tool
provided with e2fsprogs can resize ext2/3 filesystems created by parted because
it is backwards compatible, but parted can't resize (or correctly read the
structures to determine the minimum safe size) of newer ext2/3 filesystems.

I can't figure out a way to get resize2fs to tell me what the minimum safe size
is. I thought about trying to use libext2 directly, but I need to do this from
Python and there are no Python bindings for libext2. I've only been using Python
for about a month, so I'm not exactly up to writing the bindings myself.

Does anyone know of any other method for determining the minimum safe size for a
resize operation on a ext2/3 filesystem?

--
Andrew Gaffney
Network Administrator
Skyline Aeronautics, LLC.
636-357-1548


--
gentoo-user@gentoo.org mailing list