I got this error message when running dmesg
EXT3-fs (sdd1): using internal journal
EXT3-fs (sdd1): mounted filesystem with ordered data mode
EXT4-fs (sda1): warning: mounting fs with errors, running e2fsck is recommended
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts:
EXT4-fs (sdb1): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts:
EXT4-fs (sdc1): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts:
Adding 4194296k swap on /dev/sdd2. Priority:-1 extents:1 across:4194296k SSD
kjournald starting. Commit interval 5 seconds
EXT3-fs (loop0): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (loop0): using internal journal
sdd seems to be running fine. That's the main partition.
sda to sdc doesn't work. Should I umount and fo fsck? But which fsck I should use? e2fsck? e4fsck? Which one? I am using ext4 here.
I have no idea what loop0 is.
Looks like the system is pretty badly set up.
EXT3-fs (loop0): mounted filesystem with ordered data mode
I've heard I can do shutdown -rf . Someone have done that. The system is back online but I still got this message. What gives?
Best Answer
fsck
is the original name for this tool. When new file systems came out they would need specific tools for each one. Sofsck
just acts as a frontend and will call the appropriate filesystem *fsck for operations that it's not able to do itself.excerpt from the fsck man page
Most of the normal operations can be handled just by
fsck
.other tools?
A quick look on my Fedora 14 system shows the following fsck* tools:
This
locate
command shows even more:Between the 2 listings you can see that pretty much every file system type has its own fsck* tool. A few of the tools are multi-purpose such as
dos2fsck
:References