Quoting Riccardo Mottola (2015-04-01 16:17:10) > Since it appears tightly related with the FS (I was able to boot with > one or several reboots into recovery and forcing fsck) I am clearly > concerned that the shutdown is never clean, so it all adds up creating > uncertainty. > > Can we understand why my shutdown is not clean?
No. Although the shutdown sometimes hangs, it is quite reliable nowadays. Just do a normal sysvinit shutdown (e.g. use halt, or shutdown). That being said, there are two issues that fsck will constantly complain about: /dev/hd0s1: Deleted inode 95849 has zero dtime. FIXED. This is somewhat benign, but they accumulate until there is no free inode left. Then ext2fs crashes. Affects only the root filesystem. Solution: fsck every now and then. Proper solution: kill almost all processes, then umount the root filesystem. We will be able to do this with the bootshell. /dev/hd0s1: i_file_acl_hi for inode 81872 (/proc) is 32, shoud be 0. This is actually a bug in fsck, fixed upstream. Cheers, Justus
