All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: Kai Makisara <Kai.Makisara@kolumbus.fi>
Cc: "Surekha.PC" <surekhap@cisco.com>, linux-scsi@vger.kernel.org
Subject: Re: Sysfs does not recognise tape devices ?
Date: Fri, 07 Nov 2003 09:00:29 +1000	[thread overview]
Message-ID: <3FAAD28D.4050803@torque.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0311052318250.2344@kai.makisara.local>

Kai Makisara wrote:
> On Wed, 5 Nov 2003, Surekha.PC wrote:
> 
> 
>>Hi,
>>
>>I have a iSCSI setup with scsi disk and tape configured as iSCSI
>>targets. The disks are recognised with sysfs, but tape device entries
>>are not getting created.
>>
> 
> The tapes should be visible as SCSI devices in, e.g.,
> /sys/bus/scsi/devices/. You can find disks in /sys/block. The tapes belong
> to /sys/cdev but it is a very new addition to sysfs and the code to show
> the tapes there has not been done yet. It should be very easy based on
> Doug Gilberts code for sg but the feature freeze will prevent adding it
> to the official kernel for some time.

Kai,
It would be interesting to see what model you propose for
/sys/cdev and st. I felt that the cdev mechanism
was "three-quarter baked" when I used it for sg. It is flat
with no obvious support for driver parameters (unless I set
up a dummy "device" like /sys/cdev/major/sg/<driver_params>).

For a tape device the /sys/class/scsi_device/<h:c:t:l>/device
directory should have a symlink called "tape" but what to?
The st driver has a one to many mapping here; multiple
symlinks?

Until the st driver uses the cdev interface, linux in lk 2.6
will be limited to a maximum of 32 tape drives.

Doug Gilbert






  parent reply	other threads:[~2003-11-07  9:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05 12:25 Sysfs does not recognise tape devices ? Surekha.PC
2003-11-05 21:25 ` Kai Makisara
2003-11-06  5:24   ` Surekha.PC
2003-11-07 11:21     ` Christoph Hellwig
2003-11-06 23:00   ` Douglas Gilbert [this message]
2003-11-09 21:23     ` Kai Makisara

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=3FAAD28D.4050803@torque.net \
    --to=dougg@torque.net \
    --cc=Kai.Makisara@kolumbus.fi \
    --cc=linux-scsi@vger.kernel.org \
    --cc=surekhap@cisco.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.