http://bugzilla.kernel.org/show_bug.cgi?id=12594 ------- Comment #2 from anonymous@xxxxxxxxxxxxxxxxxxxx 2009-02-01 12:50 ------- Reply-To: akpm@xxxxxxxxxxxxxxxxxxxx (switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Sun, 1 Feb 2009 06:59:52 -0800 (PST) bugme-daemon@xxxxxxxxxxxxxxxxxxx wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=12594 > > Summary: filesystem corruption while running bonnie > Product: File System > Version: 2.5 > KernelVersion: 2.6.28.1 > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: normal > Priority: P1 > Component: ext3 > AssignedTo: fs_ext3@xxxxxxxxxxxxxxxxxxxx > ReportedBy: folkert@xxxxxxxxxxxxxx > > > mkdir /mnt/tmp /tmp/tmp ; mount -t tmpfs /dev/null /mnt > chown folkert /mnt/tmp /tmp/tmp > > and then in parallel: > while [ 1 ] ; do bonnie++ -d /tmp/tmp -s 128 -r 64 -x 1 -u folkert ; done > while [ 1 ] ; do bonnie++ -d /mnt/tmp -s 128 -r 64 -x 1 -u folkert ; done > > then after say 15 minutes i run the reboot command (normal via init) during the > fsck (I always do a touch /forcefsck) I get: > fsck 1.41.3 (12-Oct-2008) > /dev/mapper/VGODR-tmp contains a file system with errors, check forced. > /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (1) has > invalid depth (2) > /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (1) not > referenced > /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (2) has > invalid depth (2) > /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (2) not > referenced > /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (3) has > invalid depth (2) > /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (3) not > referenced > /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (4) has > invalid depth (2) > /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (4) not > referenced > /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (5) has > invalid depth (2) > /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (5) not > referenced > /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (6) has > invalid depth (2) > /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (6) not > referenced > /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (7) has > invalid depth (2) > /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (7) not > referenced > /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (8) has > invalid depth (2) > /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (8) has bad > max hash > /dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (8) not > referenced > ... > /dev/mapper/VGODR-tmp: Problem in HTREE 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? -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. -- 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
