From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergei Shtylyov Subject: Re: What's in libata-dev.git Date: Mon, 11 Sep 2006 17:47:31 +0400 Message-ID: <450568F3.3020005@ru.mvista.com> References: <20060911132250.GA5178@havoc.gtf.org> <45056627.7030202@ru.mvista.com> <450566A2.1090009@garzik.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from h155.mvista.com ([63.81.120.155]:4403 "EHLO imap.sh.mvista.com") by vger.kernel.org with ESMTP id S1750761AbWIKNpT (ORCPT ); Mon, 11 Sep 2006 09:45:19 -0400 In-Reply-To: <450566A2.1090009@garzik.org> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Jeff Garzik Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, Andrew Morton , Linus Torvalds Hello. Jeff Garzik wrote: >>> The following libata changes are queued for 2.6.19: >>> >>> General >>> ------- >>> * Increase lba28 max sectors from 200 to 256 >> >> >> [...] >> >>> Jeff Garzik: >> >> [...] >> >>> [ATA] Increase lba48 max-sectors from 200 to 256. >> So was it for LBA28 or for LBA48? >> As for LBA28, it might be quite dangerous. Particularly, I know >> that IBM drives used to mistreated 256 as 0 in the past (bumped into >> that on a 8-year old drive which is still alive though). > That's a typo. The first description ("lba28") is correct. > Let me know if your IBM drive has problems with current > libata-dev.git#upstream... It's not likely I'll be able to try it. But I'm absolutely sure that drive aborted the read commands with the sector count of 0 (i.e. 256 actually). The exact model was IBM DHEA-34331. 255 sectors actually seems more safe bet. WBR, Sergei