Hi Ted, The hardware is a stable product that has been in use for a while. We have experienced a number of issues with the toolchain that we received from the vendor. They are about to release a new, official version this week. So, I will try this test again with the new toolchain at some point soon. Thanks to you and Eric for the replies. Best, Sri On Sat, Dec 14, 2013 at 1:59 AM, Theodore Ts'o <tytso@xxxxxxx> wrote: > On Fri, Dec 13, 2013 at 06:33:22PM -0500, Srivatsan Canchivaram wrote: >> Hello, >> >> I found that the segmentation fault occurs in optimized code (-O2). It >> does not happen when optimization is turned off. I am not sure what >> exactly happened but mke2fs is now able to get past that point. > > This is really starting to smell like a compiler bug. Are you sure > you are using a stable version of gcc? > >> The command now fails at a different point: >> >> ext2fs_mkdir: EXT2 directory corrupted while creating /lost+found >> >> Tracing from the ext2fs_mkdir() function, I found that the code >> returns an error here: >> ext2fs_read_dir_block3(): returns EXT2_ET_DIR_CORRUPTED > > The mke2fs program has just created the root directory, and when it is > trying to link the newly created lost+found directory to the root > directory, when it reads in the just-created root directory, when it > tries to byte-swap the directory block, the values found the root > directory were insane. > > Combined with the fact that the other failure was someplace completely > diferent, I'm at this point deeply suspicious about your compiler tool > chain and/or your hardware where you are conducting your tests. > > - Ted -- 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
