Hi Ted, Am 04.03.12 21:27, schrieb Ted Ts'o: > On Sun, Mar 04, 2012 at 02:39:09PM +0000, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: >> Messages "kernel BUG at fs/ext4/extents.c:1953" occur, which seem to be >> triggered when running certain processes (reproducible with init and gdm). The >> volume can be mounted without any apparent problems and e2fsck does not report >> any errors. Nevertheless, the file system may have been corrupted during an >> earlier system crash. > Would you be willing to apply the following patch, and then see which > inode number gets reported (and whether it is always the same inode > number or one that varies) and then report back the results of running > the following debugfs commands? > > (assuming the inode number is 12345) > > debugfs /dev/sdX > > debugfs: stat <12345> > degbufs: ex <12345> In the three cases I can reproduce, the inode number has been identical. Please find the debugfs output below. Kind regards, Matthias debugfs /dev/sda2 debugfs 1.42.1 (17-Feb-2012) debugfs: stat <1312385> Inode: 1312385 Type: regular Mode: 0664 Flags: 0x80000 Generation: 1339335381 Version: 0x00000000:00000001 User: 0 Group: 406 Size: 0 File ACL: 0 Directory ACL: 0 Links: 1 Blockcount: 0 Fragment: Address: 0 Number: 0 Size: 0 ctime: 0x4f53e0ab:3c51ed20 -- Sun Mar 4 22:37:47 2012 atime: 0x4eda803c:da6fb35c -- Sat Dec 3 21:02:04 2011 mtime: 0x4f53e0ab:3bd7da30 -- Sun Mar 4 22:37:47 2012 crtime: 0x4eda803c:da6fb35c -- Sat Dec 3 21:02:04 2011 Size of extra inode fields: 28 EXTENTS: debugfs: ex <1312385> Level Entries Logical Physical Length Flags 0/ 0 1/ 1 0 - 4294967295 5276276 - 4300243571 0 -- 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
