Originally posted by Candide
View Post
(I do wonder what Michael will yell about next. Perhaps he'll complain about the harmless dtime reset messages fsck gives you if you uncleanly unmount after doing an unlink()-and-close()? Hint, fsck saying it fixed something and proceeding happily after an unclean shutdown does *not* necessarily mean something is wrong. Start to worry only if you get a fsck exit with errorcode not ORed with 4 -- i.e., a 'human intervention required' fsck -- or if you get a clean filesystem followed by ext4 assertion failure messages or -EIOs at runtime. Actual crashes suggest substantial corruption, which is definitely problematic.)
Leave a comment: