Sid Boyce wrote:
Hylton Conacher (ZR1HPC) wrote:
Looking into running a periodic check on my partitions to check for bad sectors.
Reading the man pages on fsck and e2fsck I decided that e2fsck was the better of the two for this purpose and therefore will use the command:
#> e2fsck -ccfpvC 0 </dev/hdxx>
The above command will as per the man page: e2fsck -cc This option causes e2fsck to run the badblocks(8) program If this option is specified twice, then the bad block scan will be done using a non-destructive read-write test. -f Force checking even if the file system seems clean. -p Automatically repair ("preen") the file system without any questions. -v Verbose mode on -C 0 This option causes e2fsck to write completion information to the specified file descriptor so that the progress of the filesystem check can be monitored. This option is typically used by programs which are running e2fsck. If the file descriptor specified is 0, e2fsck will print a completion bar as it goes about its business. This requires that e2fsck is running on a video console or terminal.
Do I specify a double option(-c) as above? Is this advised over a single c ie which is better to detect fs errors and repair them?
You installed ext2 partitions? EXT2 died since about SuSE 6.x or is this an old distro? Thankfully not, I have all my partitions ext3. Reading the man page I see that fsck is more for ext2 fs while e2fsck is for ext3 ones.
If you have reiserfs, don't try e2fsck on it, it gives horrible errors, thankfully when I acccidentally did it some years back, it didn't do any damage, just put up strange errors. I have the ability for Reiser but happen to be comfortable with ext3, and happen to know it has a longer track record.
-- The e2fsck Little Helper ======================================================================== Hylton Conacher - Linux user # 229959 at http://counter.li.org Currently using SuSE 9.0 Professional with KDE 3.1 Licenced Windows user ========================================================================