Fsck: Difference between revisions
From Hackepedia
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
The '''filesystem consistency check and interactive repair''' program is needed on several [[UBO]] [[filesystem]]s. When a [[filesystem]] is not properly unmounted before a reboot or halt the filesystem must be checked and any inconsistencies repaired. This can be a lengthy process and [[FreeBSD]] has a background fsck so that the system can start while it works away at making the filesystem consistent. | The '''filesystem consistency check and interactive repair''' program is needed on several [[UBO]] [[filesystem]]s. When a [[filesystem]] is not properly unmounted before a reboot or halt the filesystem must be checked and any inconsistencies repaired. This can be a lengthy process and [[FreeBSD]] has a background fsck so that the system can start while it works away at making the filesystem consistent. | ||
If you | If you shut down improperly on Linux and know you will have to answer "yes" many times, you can simply add the -y flag which means say yes to the prompts: | ||
# fsck -y | # fsck -y | ||
If you have a journaled filesystem you don't need to fsck. | |||
Revision as of 14:21, 20 November 2005
The filesystem consistency check and interactive repair program is needed on several UBO filesystems. When a filesystem is not properly unmounted before a reboot or halt the filesystem must be checked and any inconsistencies repaired. This can be a lengthy process and FreeBSD has a background fsck so that the system can start while it works away at making the filesystem consistent.
If you shut down improperly on Linux and know you will have to answer "yes" many times, you can simply add the -y flag which means say yes to the prompts:
# fsck -y
If you have a journaled filesystem you don't need to fsck.
