On Nov 14, 2008 13:49 +0100, Andreas Schultz wrote: > > Unfortunately, ltrace doesn't show what is calling this code, so > > a stack trace is needed from GDB. > > Got the same problem, here is a GDB backtrace done on Ubuntu Intrepid, > e2fsprogs 1.41.3: > > (gdb) bt > #0 0x00007fa619228bcc in ext2fs_new_block (fs=0x1fea860, goal=263012, map=0x1feaa30, ret=0x7fff21668cac) at /build/buildd/e2fsprogs-1.41.3/lib/ext2fs/alloc.c:166 > #1 0x000000000040408d in resize_inode (fs=0x1fea860, new_size=<value optimized out>) at /build/buildd/e2fsprogs-1.41.3/misc/tune2fs.c:1020 > #2 0x0000000000404d83 in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/e2fsprogs-1.41.3/misc/tune2fs.c:1638 Ah, it is trying to find free blocks, but the e2fsprogs allocator is very inefficient, IIRC, doing a linear scan of the filesystem. We probably would be far better off to generate an RB tree of the block maps so that it is easier to work with lists of blocks that need to be moved or marked in use for the resized inode table. Cheers, Andreas -- Andreas Dilger Sr. Staff Engineer, Lustre Group Sun Microsystems of Canada, Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
