Re: scsi "target1:0:0"

[James Bottomley <jejb@steeleye.com>]

On Tue, 2004-11-16 at 10:21, Kay Sievers wrote:
> We got an additional directory in the /devices directory which
> changed:
>   /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/host1/1:0:0:0
> 
> to:
>   /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/host1/target1:0:0/1:0:0:0
> 
> The inserted "target1:0:0" is _not_ backed by any "bus" or "class" device
> and therefore breaks the logic of HAL to bring the devices together by
> its parent. (We also don't get hotplug events for the "target*" device at
> creation time)

Could you explain what specific problem this causes.  You do get a
hotplug for the LUNs; a target is simply an additional node in the tree.

> Is this intentional and we can not expected a straight chain of devices
> anymore like it always was? Shouldn't there be a "class" device to have
> it consistent again.

Essentially yes.  a target is simply a LUN container.  It has no real
existence (it's created when the first lun is encountered and destroyed
when the last LUN is removed).  It's job is really to hold parameters
that apply to all LUNs.

James