From: Christoph Hellwig <hch@lst.de>
To: "Kenneth R. Crudup" <kenny@panix.com>
Cc: linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Issues with commit 34b48db6 ("block: remove artifical max_hw_sectors cap")
Date: Tue, 23 Dec 2014 09:31:40 +0100 [thread overview]
Message-ID: <20141223083140.GB2303@lst.de> (raw)
In-Reply-To: <alpine.DEB.2.10.1412211420560.4323@tosh-p75a>
On Sun, Dec 21, 2014 at 02:44:20PM -0800, Kenneth R. Crudup wrote:
>
> I had issues with my Samsung 4GB disk recently in Linus' master tree kernels,
> and have bisected it to the above commit. When doing running bonnie++ (etc.
> I get EIOs.
>
> Some info is below, let me know if you need anything else. Is there a "quirks"
> available for this option so I may special-case this particular disk?
Looks like we need to quirk it. Can you try to echo different limits
to the /sys/block/sdc/queue/max_hw_sectors_kb file for the device to
find the limit
for it?
next parent reply other threads:[~2014-12-23 8:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.10.1412211420560.4323@tosh-p75a>
2014-12-23 8:31 ` Christoph Hellwig [this message]
2014-12-24 7:48 ` Issues with commit 34b48db6 ("block: remove artifical max_hw_sectors cap") Kenneth R. Crudup
2014-12-24 8:18 ` Kenneth R. Crudup
2014-12-27 15:13 ` Christoph Hellwig
2014-12-29 3:10 ` Alan Stern
2014-12-30 11:28 ` Christoph Hellwig
2014-12-30 15:34 ` Alan Stern
2014-12-30 15:50 ` James Bottomley
2014-12-30 16:12 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1412301109050.32416-100000-pYrvlCTfrz9XsRXLowluHWD2FQJk+8+b@public.gmane.org>
2014-12-30 16:25 ` James Bottomley
2014-12-30 16:45 ` Alan Stern
2014-12-30 16:54 ` James Bottomley
2014-12-30 16:19 ` Douglas Gilbert
2014-12-30 16:36 ` Kenneth R. Crudup
2015-01-05 17:19 ` Christoph Hellwig
2015-01-05 20:07 ` Alan Stern
2015-01-05 20:19 ` Kenneth R. Crudup
2015-01-19 9:45 ` Kenneth R. Crudup
2015-01-19 15:55 ` Alan Stern
2015-01-19 22:59 ` Kenneth R. Crudup
2015-02-08 22:11 ` Kenneth R. Crudup
2015-01-05 17:18 ` Christoph Hellwig
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=20141223083140.GB2303@lst.de \
--to=hch@lst.de \
--cc=kenny@panix.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@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