Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

It seems fsck.ext4 quit very soon, I guess it only checks the journal logs, and do nothing if the journal is clean. Is it? How to force it to check the whole file system? I've tried the -f option, but it quits again said it's clean very quickly.

share|improve this question
up vote 7 down vote accepted

Try: fsck -pvcf -- will force a verbose check for bad blocks and automatically repair. If you still have issues then your HDD might have physical problems.

share|improve this answer
Make sure that the filesystem is NOT mounted before performing a fsck command. – mdpc Jul 23 '11 at 4:25

On my machine, e2fsck -fv <ext4-device> takes a long while, about two to four minutes (the device is about 360 GiB full). So I assume it does a full check! I usually use e2fsck -vfp -C0 <ext4-device>, "-p" makes automatic fixing, "-C0" prints progress to stdout, and "-v" is for "verbose".

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.