directory inode 69634: node (523) >> not >> referenced >> /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (524) >> has >> invalid depth (2) >> /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (524) >> not >> referenced >> /dev/mapper/VGODR-tmp: Invalid HTREE directory inode 69634 >> (/tmp/Bonnie.3813). >> >> I've got a gzip'ed dump of /tmp available on request. > > htree went bad. It's strange that exercising tmpfs would do this. > > I always get worried when I see device-mapper in the picture. It has a > history.. Perhaps you can describe your device-mapper setup? Hello, Sorry if this message misses the thread. Could this be connected ? http://marc.info/?l=linux-ext4&m=123755620515122&w=2 Ext3/ext4 corruption on block ramdisk. Also HTREE is corrupted under stress tests with several concurrent fsstress (LTP util) processes. Tested on latest 2.6.29-rc8 kernels, on quad Xeon machine with enough RAM. Testcase: http://marc.info/?l=linux-kernel&m=122666866015665&w=2 Denis -- 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
