From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: What's in libata-dev.git
Date: Mon, 11 Sep 2006 17:47:31 +0400 [thread overview]
Message-ID: <450568F3.3020005@ru.mvista.com> (raw)
In-Reply-To: <450566A2.1090009@garzik.org>
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
next prev parent reply other threads:[~2006-09-11 13:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 13:22 What's in libata-dev.git Jeff Garzik
2006-09-11 13:35 ` Sergei Shtylyov
2006-09-11 13:37 ` Jeff Garzik
2006-09-11 13:47 ` Sergei Shtylyov [this message]
2006-09-11 13:49 ` Jeff Garzik
2006-09-11 14:53 ` Linus Torvalds
2006-09-11 15:24 ` Jeff Garzik
2006-09-12 8:42 ` Helge Hafting
2006-09-13 1:50 ` Tejun Heo
2006-09-11 15:02 ` Alan Cox
2006-09-11 14:44 ` Jeff Garzik
2006-09-11 15:05 ` Sergei Shtylyov
2006-09-11 15:28 ` Alan Cox
2006-09-11 15:21 ` Sergei Shtylyov
2006-09-11 15:37 ` Jens Axboe
2006-09-11 15:50 ` Jeff Garzik
2006-09-11 20:01 ` Jens Axboe
2006-09-11 20:14 ` Jeff Garzik
2006-09-11 20:23 ` Jens Axboe
2006-09-11 16:04 ` Linus Torvalds
2006-09-11 19:51 ` Jens Axboe
2006-09-11 23:00 ` Alan Cox
2006-09-11 22:53 ` Greg Freemyer
2006-09-12 5:22 ` Jens Axboe
2006-09-11 16:26 ` Alan Cox
2006-09-11 19:51 ` Jens Axboe
2006-09-11 15:06 ` Jens Axboe
2006-10-04 17:57 ` Mark Lord
2006-10-04 18:03 ` Sergei Shtylyov
2006-10-04 18:48 ` Mark Lord
-- strict thread matches above, loose matches on Subject: below --
2007-01-24 7:26 Jeff Garzik
2007-01-24 17:26 ` Mark Lord
2007-01-24 19:19 ` Jeff Garzik
2006-05-24 7:08 Jeff Garzik
2006-04-18 9:54 Jeff Garzik
2006-04-18 15:07 ` Bastiaan Jacques
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=450568F3.3020005@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).