Score:0

Explanation of errors found by fsck on ext4 filesystem

sz flag

I restarted my system from the terminal using shutdown -r now (instead of the usual option in the menu), and then I ran fsck on the filesystem and got errors like:

Free blocks count wrong ...
Free inodes count wrong ...
Clearing orphaned inode ...

And it fixed them.

Were any of these errors serious? Should I be worried there might be lingering corruption in my filesystem?

Thanks!

heynnema avatar
ru flag
Occasionally run `fsck`, especially after a hang/freeze/crash. Monitor for further errors.
Score:1
ru flag

To properly check your file system...

  • boot to a Ubuntu Live DVD/USB in “Try Ubuntu” mode
  • open a terminal window by pressing Ctrl+Alt+T
  • type sudo fdisk -l
  • identify the /dev/sdXX device name for your "Linux Filesystem"
  • type sudo fsck -f /dev/sdXX, replacing sdXX with the number you found earlier
  • repeat the fsck command if there were errors
  • type reboot
Score:1
jp flag
Dan

These are not errors. They are standard info messages.

You say that fsck fixed them, so there's nothing to worry about. It is not necessarily because you used shutdown -r. It could be due to a lot of different reasons.

As long as fsck was successful, there's no reason to be alarmed.

heynnema avatar
ru flag
Of course these ARE errors. Not horrible ones, but errors none the less.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.