From 7dc435082e384d9b2d15ab53aebcde53b4aa01ab Mon Sep 17 00:00:00 2001 From: Theodore Ts'o Date: Mon, 12 Jun 2000 16:45:30 +0000 Subject: [PATCH] badblocks.8.in: Update man page explanation for badblocks. Update man page's explanation for the -c option. --- misc/badblocks.8.in | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/misc/badblocks.8.in b/misc/badblocks.8.in index 264ccd8..c08b6be 100644 --- a/misc/badblocks.8.in +++ b/misc/badblocks.8.in @@ -55,10 +55,8 @@ mode. If you set the number-of-blocks parameter to too high a value, .B badblocks will exit almost immediately with an out-of-memory error "while allocating buffers". If you set it too low, however, for a non-destructive-write-mode -test, then you are less likely to detect questionable blocks on an unreliable -hard drive (i.e., one that holds its data for a while even in bad areas, but -which loses the data in truely bad blocks, over time), since the -read-and-compare stage of the test will occur sooner after the data is written. +test, then it's possble for questionable blocks on an unreliable +hard drive to be hidden by the effects of the hard disk track buffer. .TP .BI \-i " input_file" Read a list of already existing known bad blocks. -- 1.8.3.1