From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262677AbTJTRcN (ORCPT ); Mon, 20 Oct 2003 13:32:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262687AbTJTRcN (ORCPT ); Mon, 20 Oct 2003 13:32:13 -0400 Received: from thebsh.namesys.com ([212.16.7.65]:18407 "HELO thebsh.namesys.com") by vger.kernel.org with SMTP id S262677AbTJTRcL (ORCPT ); Mon, 20 Oct 2003 13:32:11 -0400 Message-ID: <3F941C19.7030902@namesys.com> Date: Mon, 20 Oct 2003 21:32:09 +0400 From: Hans Reiser User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Mudama, Eric" CC: Norman Diamond , "'Wes Janzen '" , "'Rogier Wolff '" , "'John Bradford '" , linux-kernel@vger.kernel.org, nikita@namesys.com, "'Pavel Machek '" , "'Justin Cormack '" , "'Russell King '" , "'Vitaly Fertman '" , "'Krzysztof Halasa '" Subject: Re: Blockbusting news, results are in References: <785F348679A4D5119A0C009027DE33C105CDB30C@mcoexc04.mlm.maxtor.com> In-Reply-To: <785F348679A4D5119A0C009027DE33C105CDB30C@mcoexc04.mlm.maxtor.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Mudama, Eric wrote: >>-----Original Message----- >>From: Hans Reiser [mailto:reiser@namesys.com] >>Sent: Sunday, October 19, 2003 2:25 AM >>To: Norman Diamond >>Cc: Mudama, Eric; 'Wes Janzen '; 'Rogier Wolff '; 'John Bradford '; >>linux-kernel@vger.kernel.org; nikita@namesys.com; 'Pavel Machek '; >>'Justin Cormack '; 'Russell King '; 'Vitaly Fertman '; >>'Krzysztof Halasa >>' >>Subject: Re: Blockbusting news, results are in >> >> >>Norman Diamond wrote: >> >> >> >>>>What would you like "us disk makers" to say? >>>> >>>> >>>> >>>> >>>How to force reallocations even when data are lost, >>> >>> >>> >>buy Maxtor and write to them, thereby triggering the remap. >> >> > >It isn't necessarilly that simple. ] > Can you explain? >However, if the drive is still alive, it >has written your data to a place where it can get at it again. > > > > -- Hans