From: Willem Riede <wrlk@riede.org>
To: dougg@torque.net
Cc: linux-scsi@vger.kernel.org, Kai.Makisara@kolumbus.fi
Subject: Re: devices with more than one node
Date: Sun, 18 Jan 2004 17:08:02 -0500 [thread overview]
Message-ID: <20040118220802.GA25501@linnie.riede.org> (raw)
In-Reply-To: <4006499A.4070302@torque.net> (from dougg@torque.net on Thu, Jan 15, 2004 at 03:04:42 -0500)
On 2004.01.15 03:04, Douglas Gilbert wrote:
>
> To test it I modded scsi_debug to fake OnStream tape
> drives and ran a 2.6.1-mm2 kernel. The attached
> output of "cd /sys/class; tree scsi* osst" is instructive.
> Two peculiar entries are:
> scsi_generic/sg0/driver -> ../../../bus/scsi/drivers/osst
> scsi_generic/sg1/driver -> ../../../bus/scsi/drivers/osst
>
> This symlink only appears if the osst driver is loaded
> _before_ the sg driver! It is also left dangling by
> "rmmod osst".
I see the same with real OnStream tape drives.
It appears that when an upper level driver like osst is
(un)loaded, your (sg) attach doesn't get a chance to
reconsider...
By the way, I notice that st produces links in scsi_device
that osst doesn't - 0:0:3:0 and 3:0:0:0 are OnStream drives:
scsi_device
|-- 0:0:3:0
| `-- device -> ../../../devices/pci0000:00/0000:00:0e.0/host0/0:0:3:0
|-- 0:0:6:0
| `-- device -> ../../../devices/pci0000:00/0000:00:0e.0/host0/0:0:6:0
|-- 1:0:0:0
| |-- device -> ../../../devices/pci0000:00/0000:00:0e.1/host1/1:0:0:0
| `-- driver -> ../../../bus/scsi/drivers/sd
|-- 1:0:1:0
| |-- device -> ../../../devices/pci0000:00/0000:00:0e.1/host1/1:0:1:0
| `-- driver -> ../../../bus/scsi/drivers/sd
|-- 2:0:0:0
| |-- device -> ../../../devices/pci0000:00/0000:00:07.1/ide0/0.1/host2/2:0:0:0
| `-- driver -> ../../../bus/scsi/drivers/st
|-- 3:0:0:0
| `-- device -> ../../../devices/pci0000:00/0000:00:07.1/ide1/1.0/host3/3:0:0:0
`-- 4:0:0:0
|-- device -> ../../../devices/pci0000:00/0000:00:07.1/ide1/1.1/host4/4:0:0:0
`-- driver -> ../../../bus/scsi/drivers/st
Should I emulate what st does to create these entries?
Thanks, Willem Riede.
next prev parent reply other threads:[~2004-01-18 22:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 19:38 devices with more than one node Olaf Hering
2004-01-13 19:46 ` Greg KH
2004-01-13 21:11 ` Olaf Hering
2004-01-13 21:20 ` Greg KH
2004-01-13 23:01 ` Patrick Mansfield
2004-01-13 23:01 ` Patrick Mansfield
2004-01-13 23:18 ` Greg KH
2004-01-13 23:18 ` Greg KH
2004-01-14 1:12 ` dougg
2004-01-14 1:12 ` dougg
2004-01-14 1:26 ` Greg KH
2004-01-14 1:26 ` Greg KH
2004-01-14 3:08 ` Willem Riede
2004-01-15 8:04 ` Douglas Gilbert
2004-01-15 23:21 ` Greg KH
2004-01-16 9:59 ` Mike Anderson
2004-01-18 22:08 ` Willem Riede [this message]
2004-01-14 17:29 ` Olaf Hering
2004-01-14 17:39 ` Greg KH
2004-01-14 17:44 ` Greg KH
2004-01-14 19:15 ` Olaf Hering
2004-01-14 21:32 ` Greg KH
2004-01-14 21:35 ` Greg KH
2004-01-15 8:01 ` Vojtech Pavlik
2004-01-15 9:04 ` Olaf Hering
2004-01-15 9:19 ` Vojtech Pavlik
2004-01-15 21:18 ` Greg KH
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=20040118220802.GA25501@linnie.riede.org \
--to=wrlk@riede.org \
--cc=Kai.Makisara@kolumbus.fi \
--cc=dougg@torque.net \
--cc=linux-scsi@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.