From: Mike Christie <mchristi@redhat.com>
To: "Kamble, Nitin A" <Nitin.Kamble@Teradata.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: SCSI inquiry interface for RBD devices
Date: Fri, 12 Aug 2016 12:19:41 -0500 [thread overview]
Message-ID: <57AE052D.1040505@redhat.com> (raw)
In-Reply-To: <27148ED4-95A8-4E8F-86C0-52CEEA9140E1@Teradata.com>
On 08/11/2016 06:38 PM, Kamble, Nitin A wrote:
>
> SCSI block devices has SG_IO IOCTL interface by which applications can identify the device uniquely. This helps applications identify the device uniquely without relying on the device file names or any other mechanisms.
>
> For more details l ook at the manpage of sg_inq commnad. https://manned.org/sg_inq
>
> Some of the non SCSI devices also support this SG_IO interface for inquiry. Examples include SATA, NVME, Virtual Disks.
>
> It is desired to identify every RBD uniquely just from the device file. It will help in using RBD devices as drop in replacement for SCSI/SATA devices. Currently the RBD code in ceph-client does not support the SG_IO ioctl interface for inquiry to identify the device uniquely. Has adding the SG_IO ioctl interface to the RBD devices ever been considered before?
>
What application do you need this for right now? Is it udev's scsi_id?
What pages do you need? Just 0x83?
next prev parent reply other threads:[~2016-08-12 17:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 23:38 SCSI inquiry interface for RBD devices Kamble, Nitin A
2016-08-12 14:17 ` Ilya Dryomov
2016-08-12 17:29 ` Ilya Dryomov
2016-08-12 17:42 ` Kamble, Nitin A
2016-08-12 18:15 ` Ilya Dryomov
2016-08-12 18:40 ` Kamble, Nitin A
2016-08-13 15:18 ` Alex Elder
2016-08-13 19:14 ` Ilya Dryomov
2016-08-24 18:44 ` Alex Elder
2016-08-12 17:19 ` Mike Christie [this message]
2016-08-12 18:23 ` Kamble, Nitin A
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=57AE052D.1040505@redhat.com \
--to=mchristi@redhat.com \
--cc=Nitin.Kamble@Teradata.com \
--cc=ceph-devel@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 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.