/me wonders, whether the following messages should force me to *immediately* reboot the system of whether I should schedule a reboot in the near future : 2012-11-19T19:23:53.099+01:00 n22 kernel: EXT4-fs error (device sdb3) in ext4_new_inode:933: IO failure 2012-11-19T19:24:04.971+01:00 n22 kernel: EXT4-fs error (device sdb3): ext4_mb_generate_buddy:741: group 409, 11806 clusters in bitmap, 11805 in gd 2012-11-19T19:24:04.971+01:00 n22 kernel: JBD2: Spotted dirty metadata buffer (dev = sdb3, blocknr = 0). There's a risk of filesystem corruption in case of system crash. 2012-11-19T19:37:20.188+01:00 n22 kernel: EXT4-fs error (device sdb3) in ext4_new_inode:933: IO failure 2012-11-19T19:44:28.552+01:00 n22 kernel: EXT4-fs error (device sdb3): ext4_mb_generate_buddy:741: group 424, 27235 clusters in bitmap, 27234 in gd 2012-11-19T19:44:28.552+01:00 n22 kernel: JBD2: Spotted dirty metadata buffer (dev = sdb3, blocknr = 0). There's a risk of filesystem corruption in case of system crash. 2012-11-19T19:44:33.734+01:00 n22 kernel: EXT4-fs error (device sdb3): mb_free_blocks:1300: group 424, block 13916749:freeing already freed block (bit 23117) 2012-11-19T19:44:33.734+01:00 n22 kernel: EXT4-fs error (device sdb3): mb_free_blocks:1300: group 409, block 13431904:freeing already freed block (bit 29792) -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 -- 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
