Question

1

Explanation of errors found by fsck on ext4 filesystem

rated 0 times [ 1] [ 0] / answers: 1 / hits: 1056 / 2 Years ago, thu, april 7, 2022, 6:32:40

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!

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

ciousuntru

Add To Favorites

Follow

Total Points: 352

Total Questions: 124

Total Answers: 95

Location: Grenada

Member since Tue, Oct 12, 2021

3 Years ago

ciousuntru questions

1 How to filter rows in a csv file with bash based in two conditions?

Sat, Dec 17, 22, 21:00, 1 Year ago

1 How do I stop my ROG Falchion wireless keyboard from rebooting Ubuntu?

Tue, Aug 17, 21, 06:37, 3 Years ago

1 Lubuntu 20.04 cannot execute .sh script from PCManFM-Qt

Tue, Jan 24, 23, 02:14, 1 Year ago

1 "Always on top" option missing for Firefox/Chrome in 18.04

Sat, Dec 18, 21, 21:37, 2 Years ago

1 What is the default terminal for Ubuntu?

Mon, May 30, 22, 05:42, 2 Years ago

View All

answered 2 Years ago iedncommon · Accepted Answer

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.