Hans Reiser [EMAIL PROTECTED] writes:
Just taking a guess, many hard drives have difficult and time-consuming
procedures that they can go through to read a troublesome block. These
can take 20-30 seconds. Probably if they have to go through these
procedures, once they finally succeed the
Matthias Andree wrote:
Hans Reiser [EMAIL PROTECTED] writes:
Just taking a guess, many hard drives have difficult and time-consuming
procedures that they can go through to read a troublesome block. These
can take 20-30 seconds. Probably if they have to go through these
procedures, once
On Tue, 20 Aug 2002, Hans Reiser wrote:
Vitaly, take a look at that. Part of a good user interface is letting
users know what tools are available. Remember, most users will
encounter a failing drive and/or fsck on a journaling fs as a rare and
stressful event in their lives, so it is
Oleg Drokin [EMAIL PROTECTED] writes:
Basically uyou'd better search for this on HDD vendors sites.
What's going on is simply can be described this way:
You write some block to HDD, if HDD decides the block is bad for some reason
and remapping is allowed (usually by tiurning on
Oleg Drokin wrote:
Hello!
Basically uyou'd better search for this on HDD vendors sites.
What's going on is simply can be described this way:
You write some block to HDD, if HDD decides the block is bad for some reason
and remapping is allowed (usually by tiurning on SMART), block is
