Message-ID: <454EA263.4090008@cfl.rr.com>
Date: Sun, 05 Nov 2006 21:48:03 -0500
From: Phillip Susi <psusi@cfl.rr.com>
User-Agent: Thunderbird 1.5.0.7 (X11/20060918)
MIME-Version: 1.0
To: Brad Campbell <brad@wasp.net.au>
CC: James Courtier-Dutton <James@superbug.co.uk>,
       Alan Cox <alan@lxorguk.ukuu.org.uk>,
       Albert Cahalan <acahalan@gmail.com>, kangur@polcom.net,
       mikulas@artax.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org
Subject: Re: New filesystem for Linux
References: <787b0d920611041159y6171ec25u92716777ce9bea4a@mail.gmail.com> <1162691856.21654.61.camel@localhost.localdomain> <454DC799.9000401@superbug.co.uk> <454DCAAC.3080903@wasp.net.au>
In-Reply-To: <454DCAAC.3080903@wasp.net.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 897
Lines: 19

Brad Campbell wrote:
> I've never seen this behaviour in a drive. All the drives I've seen mark 
> bad sectors as "pending reallocation", they they return read errors on 
> that sector unless they manage to jag a good read, in which case they 
> then reallocate the sector. Or else they wait for you to write to the 
> sector triggering a reallocation.
> 

This is exactly what they are required to do by the relevant standards. 
  The drive can not silently discard data and reallocate the sector.  It 
either has to get a successful read of the old data, then reallocate, or 
wait for the host to write new data, and store that in the new location.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/