Failures in e2fsprogs-1.39-tyt3 'make check'
Hi all, I'm getting some errors in the 'make check' step when building e2fsprogs-1.39-tyt3. Many of the errors look to be as a result of missing image files, for example: f_orphan_dotdot_ft: filetype of .. in orphaned directories: ../../tests/run_e2fsck: line 43: ../../tests/f_orphan_dotdot_ft/image.gz: No such file or directory rm: cannot remove `./test.img': No such file or directory Sorry if this is a documented, known issue. I'm just being paranoid and don't want to do a 'make install' if it will hose up the box. Thanks, Kirk - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Failures in e2fsprogs-1.39-tyt3 'make check'
On Mon, Jun 04, 2007 at 01:18:23AM -0700, Kirk True wrote: Hi all, I'm getting some errors in the 'make check' step when building e2fsprogs-1.39-tyt3. Many of the errors look to be as a result of missing image files, for example: f_orphan_dotdot_ft: filetype of .. in orphaned directories: ../../tests/run_e2fsck: line 43: ../../tests/f_orphan_dotdot_ft/image.gz: No such file or directory rm: cannot remove `./test.img': No such file or directory Sorry if this is a documented, known issue. I'm just being paranoid and don't want to do a 'make install' if it will hose up the box. Yes, it's known. Note that e2fsprogs 1.39-tyt3 is really only meant for ext4 developers. If you're not trying to use ext4 (and it's really not meant for production use yet), you should be using e2fsprogs.1.39 or e2fsprogs WIP-20070407. Regards, - Ted - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Failures in e2fsprogs-1.39-tyt3 'make check'
Hi Theodore, Sorry if this is a documented, known issue. I'm just being paranoid and don't want to do a 'make install' if it will hose up the box. Yes, it's known. Note that e2fsprogs 1.39-tyt3 is really only meant for ext4 developers. If you're not trying to use ext4 (and it's really not meant for production use yet), you should be using e2fsprogs.1.39 or e2fsprogs WIP-20070407. Thanks for the quick reply. Yes - I'm trying to get into ext4 development, so I'll assume these aren't fatal and proceed. Thanks! Kirk - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: e2fsprogs-1.39-tyt3
On Apr 30, 2007 11:22 -0400, Theodore Ts'o wrote: One concern I still have is the fact that we're exposing a lot of interfaces in libext2fs.so which are very specifically tied to the current 48-bit physical/32-bit logical on-disk extent data structure. If/when we add support for the 64/64-bit extent data structure, and some kind of compressed/bit-packed extent format, those interfaces will have to be extended. Some other comments: - it appears you have all of extents.c copied into both block.c and in extent.c - it appears you are missing a couple of extent sanity checks for headers and such that were added more recently, but those might also have been removed by you - do the patches as they stand actually fix the duplicate block test cases yet? It seems all of the BLOCK_CHANGED handling was removed from block_iterate_extents(). - it would be easier to read if the patches were generated with diff -up (can be set in .quiltrc via 'export QUILT_DIFF_OPTS=-up'. I also like export QUILT_NO_DIFF_TIMESTAMPS=1 to avoid tons of gratuitous changes to patches when they are refreshed. Another problem is that while external extent blocks are getting byte swapped, there is no byte swapping going on for the extents stored in the inode. I haven't tried it on a big endian system, such as Power machine, but I'm pretty sure it's going to blow up spectacularly. Ah, interesting. We have 64-bit machines for testing, but no big-endian ones. The patches can be found at: ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs-interim/e2fsprogs-1.39-tyt3 What else I think is important to get into this patch series is a change to mkfs.ext4 so that the default inode size is increased to 256. I'm not sure how/if this can be done via mke2fs.conf. I also wouldn't object to changing the default inode_ratio on large filesystems to be a lot fewer than 1/8192 bytes. At a minimum, allowing an inode_ratio 1/4MB should be allowed. Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc. - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: e2fsprogs-1.39-tyt3
On May 01, 2007 11:05 -0400, Theodore Tso wrote: Speaking of SCM's, how wedded is Clustrefs to mercurial? I've been considering migrating e2fsprogs development to git, but one of the reasons I haven't is because I was concerned that might be incovenient for you folks. Not at all, we just generate a 1.39 to 1.39-WIP patch, and then use quilt + CVS to manage the resulting patches. Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc. - To unsubscribe from this list: send the line unsubscribe linux-ext4 in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
