From: Patrick Mansfield <patmans@us.ibm.com>
To: Willem Riede <wrlk@riede.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Badness in scsi_single_lun_run at /root/scsi/scsi_lib.c:344
Date: Wed, 28 Jan 2004 09:53:41 -0800 [thread overview]
Message-ID: <20040128095341.A5242@beaverton.ibm.com> (raw)
In-Reply-To: <20040128173609.GE23308@serve.riede.org>; from wrlk@riede.org on Wed, Jan 28, 2004 at 12:36:09PM -0500
On Wed, Jan 28, 2004 at 12:36:09PM -0500, Willem Riede wrote:
> On 2004.01.28 11:41, Patrick Mansfield wrote:
> > Do you know if the single lun code is for performance, or because of
> > hardware limitations - that is we don't want a disc change between IO, or
> > does the device just fail?
>
> In the case of the NEC PD/CD, it is a hardware limitation. You can only
> have one disc inserted at a time, either CD or PD. Mixing IO will fail
> for the absent media type.
BTW what is PD?
So there is one physical drive that can hold one disc, and it can only use
the LUN associated with the disc that is currently in the drive; and reading
or accessing the wrong LUN will always fail?
We don't need single_lun code for that, we can just let the IO fail, right?
I assume there are other single_lun devices that automatically change discs.
-- Patrick Mansfield
next prev parent reply other threads:[~2004-01-28 17:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 0:32 Badness in scsi_single_lun_run at /root/scsi/scsi_lib.c:344 Willem Riede
2004-01-28 3:30 ` Willem Riede
2004-01-28 16:41 ` Patrick Mansfield
2004-01-28 17:36 ` Willem Riede
2004-01-28 17:53 ` Patrick Mansfield [this message]
2004-01-28 18:33 ` Willem Riede
2004-01-28 18:37 ` Matthew Wilcox
2004-01-30 20:14 ` [PATCH] fix badness in scsi_single_lun_run Patrick Mansfield
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=20040128095341.A5242@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=wrlk@riede.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