From: Richard Purdie <rpurdie@rpsys.net>
To: Bob Stewart <bob@evoria.net>
Cc: Tejun Heo <htejun@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: sata_inic162x driver for 2.6.19
Date: Wed, 10 Jan 2007 23:34:32 +0000 [thread overview]
Message-ID: <1168472072.14261.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20061221041618.12158.qmail@web813.biz.mail.mud.yahoo.com>
On Wed, 2006-12-20 at 20:16 -0800, Bob Stewart wrote:
> Sorry, that should have been "logblocks". As shown below, it works unless the
> partition is such that logblocks will be larger than 16383. In fdisk, that
> number of cylinders anything greater than 16709. "Works" is relative, though.
> When doing a copy of several gigabytes, the syslog shows periodic device
> errors, which I have posted previously. Each time, it lowers the access rate
> until it eventually reaches PI04.
[...]
> Here is the fdisk screen for the above disk. If I use a figure larger than
> 16709 cylinders mkfs.xfs will not be successful.
>
> Disk /dev/sda: 200.0 GB, 200049647616 bytes
> 255 heads, 63 sectors/track, 24321 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sda1 1 16709 134215011 83 Linux
Its probably significant that the problem appears at >137GB. I've got a
similar issue with a 320GB drive I've just tried to use. I've not pinned
down the limit but I partitioned the drive in two and the first half
works, the second half gives corrupt superblock errors when trying to
mount it (ext3).
I tried both the 2.6.19 version and one based on 2.6.20-rc4, same
problem. Is there anything specific the driver needs to do work with
disks > 137GB?
I've just tried to grab the datasheet but the Initio webserver has
chosen this moment to act up...
Richard
next prev parent reply other threads:[~2007-01-10 23:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-17 1:48 [PATCH 1/2] libata: kill qc->nsect and cursect Tejun Heo
2006-12-17 1:50 ` [PATCH 2/2] sata_inic162x: finally, driver for initio 162x SATA controllers Tejun Heo
2006-12-17 12:24 ` Alan
2006-12-18 0:04 ` Tejun Heo
2006-12-18 0:25 ` Bob Stewart
2006-12-20 6:21 ` sata_inic162x driver for 2.6.19 Tejun Heo
2006-12-21 0:06 ` Bob Stewart
2006-12-21 1:48 ` Bob Stewart
2006-12-21 4:16 ` Bob Stewart
2007-01-10 23:34 ` Richard Purdie [this message]
2007-01-11 0:04 ` Alan
2007-01-11 2:00 ` Bob Stewart
2006-12-20 6:25 ` [PATCH 2/2] sata_inic162x: driver for initio 162x SATA controllers, take 2 Tejun Heo
2006-12-20 19:56 ` Jeff Garzik
2007-01-03 8:18 ` Tejun Heo
2007-01-03 8:30 ` [PATCH 1/2] libata: kill qc->nsect and cursect Tejun Heo
2007-01-03 8:32 ` [PATCH 2/2] sata_inic162x: finally, driver for initio 162x SATA controllers, take #2 Tejun Heo
2007-01-20 0:04 ` Jeff Garzik
2007-01-20 0:04 ` [PATCH 1/2] libata: kill qc->nsect and cursect Jeff Garzik
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=1168472072.14261.5.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=bob@evoria.net \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.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).