RE: [ext2resize] New ext3 online resize & e2fsprogs patches

[Poul P. <pe...@ro...>]

	I have a feeling I'm going to feel stupid when I get an answer, but
here goes:

	I'm working with 2.4.18-14 (RH) and I have applied the ext3-online
patch for 2.4.18, enabled in kernel, recompiled etc. I have also applied the
e2fsprogs 1.28 patch for resizing to, well e2fsprogs 1.28. I'm also running
ext2resize-1.1.17 which I pulled down from
http://ext2resize.sourceforge.net/ext2resize-1.1.17.tar.gz Now, when I try
to resize an online ext3 filesystem with ext2online I get the error:

ext2_open: fs has unsupported feature(s) enabled

	This message is generated at line 887 in ext2.c and the test that is
failing seems to be checking, among other things, whether or not the target
fs is ext3. Have I got the wrong tools? The patches in the test/ subdir seem
to be earlier versions of ext3online kernel patches. Offline resizing of
ext3 is working fine.

Thanks,

-poul

> -----Original Message-----
> From: Robert Walsh [mailto:rj...@du...]
> Sent: Saturday, November 02, 2002 1:01 AM
> To: ext2resize
> Cc: Andreas Dilger; Bryan O'Sullivan; Andrew Morton
> Subject: [ext2resize] New ext3 online resize & e2fsprogs patches
> 
> 
> Hi all,
> 
> I have posted new ext3 online resize patches to linux-2.4.18 and
> linux-2.4.19.  New in these patches is a fix to a problem where the
> wrong entry from the resize inode dind block was being zeroed 
> out after
> a new gdb was created.  This caused the resize to fail at seemingly
> arbitrary points, and eventually caused corruption of the filesystem.
> 
> I have also posted new patches to e2fsprogs-1.28 and e2fsprogs-1.29. 
> New in these patches is a fix to a bug in the resize inode size
> calculations to handle really large resize inodes and removal of the
> hack to e2fsck to work around this bug.  I haven't tested the patch to
> 1.29 yet, but it does compile; caveat emptor.
> 
> Note: I just noticed that e2fsprogs-1.30 has been released.  
> My initial
> attempt to apply the 1.29 patch failed, and the port looks nasty,
> actually.  I'll try get to that in the middle of November, if 
> I have the
> time.  Please use 1.28 (or 1.29, if you feel brave) for the moment.
> 
> The upshot of the above patches is that resize should now work for
> resizing any arbitrary sized filesystem to any new (larger) size.  It
> also means that the resulting filesystem passes fsck without any
> problems and no hacky workarounds.
> 
> I have tested the patches on 2.4.19 growing various sized filesystems
> from 1GB to 1TB.  Next week, I should have a chance to test them on
> filesystems from 1TB to 4TB (with large block device support.)  In the
> next month or two, I'm going to try scrape enough disks 
> together to test
> up to 16TB - I'll let you know how it goes.
> 
> All of the above patches are in the CVS tree and posted on the
> ext2resize SourceForge patch tracker page.
> 
> Let me know if you have any problems.
> 
> Regards,
>  Robert.
> 
> -- 
> Robert Walsh
> Amalgamated Durables, Inc.  -  "We don't make the things you buy."
> Email: rj...@du...
>