Hello, On Sun 28-09-14 12:44:56, Pavel Machek wrote: > After update to debian testing, my machine sometimes fails to > reboot. (aptitude upgrade seems to be the trigger). > > So I had to hard power-down the machine. That should be perfectly > safe, as ext4 has a journal, and this is plain SATA disk, right? Yes, it should be safe. > On next boot to Debian stable, I got stacktrace, and messages about > ext4 corruption. Back to Debian testing. systemd ran fsck, determined It would be really good to get those messages... Ideally you could also use e2image -r <partition> | bzip2 -c to store fs metadata before doing anything else with the fs to a usb stick. That is invaluable for future analysis. > it can't fix it, dropped me into emergency shell, _but mounted the > filesstem, anyway_. Oops. What kernel versions are you running in Debian testing and stable? My guess would be that kernel had problems only during orphan inode recovery (i.e. when deleting already deleted files) and we let the mount proceed if this fails because it's a relatively harmless problem. > Now I'm getting > > fsck 1.42.12 > ... > Inodes that were part of a corrupted orphan linked list found <y> > Deleted inode has zero dtime <y> > (6 inodes) was part of the orphaned inode list. FIXED. > Block bitmap differences. > Free inode counts wrong. Honza -- Jan Kara <jack@xxxxxxx> SUSE Labs, CR -- 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
