From: Patrick Mansfield <patmans@us.ibm.com>
To: Matthias Andree <matthias.andree@gmx.de>
Cc: Alan Stern <stern@rowland.harvard.edu>,
SCSI development list <linux-scsi@vger.kernel.org>,
Samuel Colin <Samuel.Colin3@wanadoo.fr>
Subject: Re: What is SCSI command 0xa0 ?
Date: Mon, 14 Feb 2005 13:53:30 -0800 [thread overview]
Message-ID: <20050214215330.GA14426@us.ibm.com> (raw)
In-Reply-To: <m3r7ji7rxp.fsf@merlin.emma.line.org>
On Mon, Feb 14, 2005 at 10:27:46PM +0100, Matthias Andree wrote:
> "REPORT LUNS". This is probably only useful on media changers and
> perhaps disk arrays.
Yes.
You can disable it completely or just for the broken device.
BLIST_NOREPORTLUN is 0x40000. On boot or scsi_mod loading, to disable for
all devices:
[scsi_mod.]default_dev_flags=0x40000
Or for one device:
[scsi_mod.]dev_flags="vendor:model:0x40000"
Or for one device via /proc after scsi_mod is running:
echo "vendor:model:0x40000" > /proc/scsi/device_info
-- Patrick Mansfield
next prev parent reply other threads:[~2005-02-14 21:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050214160210.6c7e7e52@hebus>
2005-02-14 21:07 ` What is SCSI command 0xa0 ? Alan Stern
2005-02-14 21:12 ` Doug Maxey
[not found] ` <Pine.LNX.4.44L0.0502141623440.1843-100000@ida.rowland.org>
2005-02-14 22:06 ` Samuel Colin
2005-02-16 16:42 ` Alan Stern
2005-02-17 15:59 ` Samuel Colin
2005-02-17 21:18 ` Magical ansi scsi revision (was Re: [linux-usb-devel] Re: What is SCSI command 0xa0 ?) Samuel Colin
2005-02-17 22:23 ` Alan Stern
2005-02-17 22:49 ` Samuel Colin
2005-02-17 22:31 ` [PATCH as470] Add a NOREPORTLUN blacklist flag Alan Stern
2005-02-20 16:59 ` Sergey Vlasov
2005-02-21 3:44 ` Alan Stern
2005-02-21 6:47 ` Matthew Dharm
2005-02-21 17:52 ` Patrick Mansfield
2005-02-21 22:07 ` Alan Stern
2005-02-28 17:26 ` James Bottomley
2005-02-28 22:27 ` Alan Stern
2005-02-14 21:27 ` What is SCSI command 0xa0 ? Matthias Andree
2005-02-14 21:53 ` Patrick Mansfield [this message]
2005-02-14 22:02 ` 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=20050214215330.GA14426@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=Samuel.Colin3@wanadoo.fr \
--cc=linux-scsi@vger.kernel.org \
--cc=matthias.andree@gmx.de \
--cc=stern@rowland.harvard.edu \
/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.