Difference between revisions of "Fsck"
From Notes_Wiki
m |
m |
||
| Line 1: | Line 1: | ||
<yambe:breadcrumb>Filesystem or partition tools</yambe:breadcrumb> | <yambe:breadcrumb self="Fsck">Filesystem or partition tools|Filesystem or partition tools</yambe:breadcrumb> | ||
=fsck= | =fsck= | ||
| Line 20: | Line 20: | ||
Note: | Note: | ||
*'''It is advisable to use e2fsck in above format so that it calls '<tt>badblocks</tt>' internally, and we should avoid calling program badblocks directly. | *'''It is advisable to use e2fsck in above format so that it calls '<tt>badblocks</tt>' internally, and we should avoid calling program badblocks directly. | ||
<yambe:breadcrumb self="Fsck">Filesystem or partition tools|Filesystem or partition tools</yambe:breadcrumb> | |||
Revision as of 10:31, 9 September 2018
<yambe:breadcrumb self="Fsck">Filesystem or partition tools|Filesystem or partition tools</yambe:breadcrumb>
fsck
Checking ext3 partitions for disk errors
We can use following command to check ext3 partitions for disk errors / surface scan for bad blocks:
e2fsck -c -c -k -v -C 0 <partition_device_name>
Here:
- -c : To call badblocks for surface scan
- -c : Repeated to indicate non-destructive read-write tests
- -k : Preserve previous list of bad blocks
- -v : Verbose
- -C 0 : To print progress on file descriptor. For some strange reason 0 causes output to be sent on screen.
Note:
- It is advisable to use e2fsck in above format so that it calls 'badblocks' internally, and we should avoid calling program badblocks directly.
<yambe:breadcrumb self="Fsck">Filesystem or partition tools|Filesystem or partition tools</yambe:breadcrumb>
