All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Chris Friesen <chris.friesen@windriver.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Jens Axboe <axboe@kernel.dk>, lkml <linux-kernel@vger.kernel.org>,
	linux-scsi@vger.kernel.org, Mike Snitzer <snitzer@redhat.com>
Subject: Re: absurdly high "optimal_io_size" on Seagate SAS disk
Date: Fri, 07 Nov 2014 14:17:37 -0500	[thread overview]
Message-ID: <yq1389u95wu.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <545D13FF.6090306@windriver.com> (Chris Friesen's message of "Fri, 7 Nov 2014 12:48:31 -0600")

>>>>> "Chris" == Chris Friesen <chris.friesen@windriver.com> writes:

Chris> Apparently the "hdparm -I" command is giving bogus data as well.
Chris> I've seen that happen if the drive is on a RAID controller--I
Chris> assume that could cause problems with firmware updates too?

I'd suggest trying /dev/sgN instead.

But yes, some RAID controllers require you to use their tooling and
won't allow direct passthrough.

-- 
Martin K. Petersen	Oracle Linux Engineering

WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Chris Friesen <chris.friesen@windriver.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Jens Axboe <axboe@kernel.dk>, lkml <linux-kernel@vger.kernel.org>,
	<linux-scsi@vger.kernel.org>, Mike Snitzer <snitzer@redhat.com>
Subject: Re: absurdly high "optimal_io_size" on Seagate SAS disk
Date: Fri, 07 Nov 2014 14:17:37 -0500	[thread overview]
Message-ID: <yq1389u95wu.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <545D13FF.6090306@windriver.com> (Chris Friesen's message of "Fri, 7 Nov 2014 12:48:31 -0600")

>>>>> "Chris" == Chris Friesen <chris.friesen@windriver.com> writes:

Chris> Apparently the "hdparm -I" command is giving bogus data as well.
Chris> I've seen that happen if the drive is on a RAID controller--I
Chris> assume that could cause problems with firmware updates too?

I'd suggest trying /dev/sgN instead.

But yes, some RAID controllers require you to use their tooling and
won't allow direct passthrough.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2014-11-07 19:17 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 16:47 absurdly high "optimal_io_size" on Seagate SAS disk Chris Friesen
2014-11-06 17:16 ` Chris Friesen
2014-11-06 17:16   ` Chris Friesen
2014-11-06 17:34   ` Martin K. Petersen
2014-11-06 17:34     ` Martin K. Petersen
2014-11-06 17:45     ` Chris Friesen
2014-11-06 17:45       ` Chris Friesen
2014-11-06 18:12       ` Martin K. Petersen
2014-11-06 18:12         ` Martin K. Petersen
2014-11-06 18:15         ` Jens Axboe
2014-11-06 19:14         ` Chris Friesen
2014-11-06 19:14           ` Chris Friesen
2014-11-07  1:56           ` Martin K. Petersen
2014-11-07  1:56             ` Martin K. Petersen
2014-11-07  5:35             ` Chris Friesen
2014-11-07  5:35               ` Chris Friesen
2014-11-07 15:18               ` Dale R. Worley
2014-11-07 16:25               ` Martin K. Petersen
2014-11-07 16:25                 ` Martin K. Petersen
2014-11-07 17:42                 ` Martin K. Petersen
2014-11-07 17:42                   ` Martin K. Petersen
2014-11-07 17:51                   ` Chris Friesen
2014-11-07 17:51                     ` Chris Friesen
2014-11-07 18:03                     ` Martin K. Petersen
2014-11-07 18:03                       ` Martin K. Petersen
2014-11-07 18:48                 ` Chris Friesen
2014-11-07 18:48                   ` Chris Friesen
2014-11-07 19:17                   ` Martin K. Petersen [this message]
2014-11-07 19:17                     ` Martin K. Petersen
2014-11-07 21:04                     ` Chris Friesen
2014-11-07 21:04                       ` Chris Friesen
2014-11-07 17:10             ` Elliott, Robert (Server Storage)
2014-11-07 17:40               ` Martin K. Petersen
2014-11-07 17:40                 ` Martin K. Petersen
2014-11-07 20:15               ` Douglas Gilbert

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=yq1389u95wu.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=chris.friesen@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=snitzer@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.