Andreas Dilger <adilger@xxxxxxx> wrote: > Nick, > sorry to be so slow getting back to you. Attached are the relatively > simple test programs we use to verify whether large block devices and > large filesystems are suffering from block address aliasing. > > The first tool (llverdev) will write either partial or fill data patterns > to the disk, then read them back and verify the data is still correct. > > The second tool (llverfs) will try to allocate directories spread across > the filesystem (if possible, using EXT2_TOPDIR_FL) and then fill the > filesystem partially or fully with a data pattern in ~1GB files and > then read them back for verification. > > This isn't really a stress test, but rather just a sanity check for > variable overflows at different levels of the IO stack. > Andreas, thanks very much! I'll do some runs over the weekend with them, as well as some e2fsck runs w/blktrace (with and without lazy itable init). Thanks, Nick PS. BTW, I have problems receiving email right now - the Reply-to address above seems to work but my "official" address in the From header does not. -- 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
