scsi device is not available in enclosure any more after hot plugging

scsi device is not available in enclosure any more after hot plugging

[Lars Täuber]

Hi there!

One of my servers contains two scsi enclosures.
After hot removing a disk and hot adding another in the same slot the new disk gets assigned a device file but the enclosure (in sysfs) doesn't want to see it.

How can I force the enclosure to recognise the hot added disk.

Situation in sysfs:
# ls -l "/sys/class/enclosure/10:0:24:0/SLOT 010"
insgesamt 0
-rw-r--r-- 1 root root 4096 2010-01-15 14:30 active
lrwxrwxrwx 1 root root 0 2010-01-15 12:56 device -> ../../../../../../../port-10:0:11/end_device-10:0:11/target10:0:10/10:0:10:0
-rw-r--r-- 1 root root 4096 2010-01-15 14:31 fault
-rw-r--r-- 1 root root 4096 2010-01-15 14:40 locate
drwxr-xr-x 2 root root 0 2010-01-15 14:01 power
-rw-r--r-- 1 root root 4096 2010-01-15 14:01 status
-r--r--r-- 1 root root 4096 2010-01-15 14:01 type
-rw-r--r-- 1 root root 4096 2010-01-15 14:01 uevent

The link «device» is dead after hot removing the device and keeps vanished after hot adding the new device.
The hot added device gets assigned a device file and it is reachable.
Even
# echo 1 > /sys/bus/scsi/devices/10\:0\:24\:0/rescan
doesn't change anything.

How can I force the link to be updated towards
-> ../../../../../../../port-10:0:26/end_device-10:0:26/target10:0:25/10:0:25:0
???


Is there a detailed description of the sysfs regarding scsi on the web?

Thanks
Lars

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

entries in sysfs regarding enclosures seem not being updated after hot plugging

[Lars Täuber]

Hallo!

I might be wrong on this mailing list. Is there a special sysfs ML?

Please point me out a place to look next with my problem.

I should have mentioned the kernel version and enclosure type:
# uname -a
Linux speicher48 2.6.31-17-server #54-Ubuntu SMP Thu Dec 10 18:06:56 UTC 2009 x86_64 GNU/Linux
# cat /sys/class/enclosure/10\:0\:24\:0/device/vendor 
CHENBRO 
# cat /sys/class/enclosure/10\:0\:24\:0/device/model 
SASX36 B0       


Regards
Lars

Re: entries in sysfs regarding enclosures seem not being updated after hot plugging

[James Bottomley]

On Wed, 2010-01-20 at 09:57 +0100, Lars Täuber wrote:
> I might be wrong on this mailing list. Is there a special sysfs ML?

No, this is the right list.

> Please point me out a place to look next with my problem.
> 
> I should have mentioned the kernel version and enclosure type:
> # uname -a
> Linux speicher48 2.6.31-17-server #54-Ubuntu SMP Thu Dec 10 18:06:56 UTC 2009 x86_64 GNU/Linux
> # cat /sys/class/enclosure/10\:0\:24\:0/device/vendor 
> CHENBRO 
> # cat /sys/class/enclosure/10\:0\:24\:0/device/model 
> SASX36 B0       

So the bug reports sound like something is going wrong in the device
unbinding ... I don't see what from the code, so I need to play with an
actual enclosure.  Unfortunately, that can only be done when physically
present (unlike most of the SCSI development which I can do remotely),
so it has to wait until I get back home.

James


--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: entries in sysfs regarding enclosures seem not being updated after hot plugging

[Lars Täuber]

Hi James!

James Bottomley <James.Bottomley@suse.de> schrieb:
> On Wed, 2010-01-20 at 09:57 +0100, Lars Täuber wrote:
> > I might be wrong on this mailing list. Is there a special sysfs ML?
> 
> No, this is the right list.

Ok.


> > Please point me out a place to look next with my problem.
> > 
> > I should have mentioned the kernel version and enclosure type:
> > # uname -a
> > Linux speicher48 2.6.31-17-server #54-Ubuntu SMP Thu Dec 10 18:06:56 UTC 2009 x86_64 GNU/Linux
> > # cat /sys/class/enclosure/10\:0\:24\:0/device/vendor 
> > CHENBRO 
> > # cat /sys/class/enclosure/10\:0\:24\:0/device/model 
> > SASX36 B0       
> 
> So the bug reports sound like something is going wrong in the device
> unbinding ... I don't see what from the code, so I need to play with an
> actual enclosure.  Unfortunately, that can only be done when physically
> present (unlike most of the SCSI development which I can do remotely),
> so it has to wait until I get back home.

Thanks. I'm looking forward to.
If I can help any further just ask. The server isn't productive yet.

Lars
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: entries in sysfs regarding enclosures seem not being updated after hot plugging

[Lars Täuber]

Hallo James,

James Bottomley <James.Bottomley@suse.de> schrieb:
> On Wed, 2010-01-20 at 09:57 +0100, Lars Täuber wrote:
> > I might be wrong on this mailing list. Is there a special sysfs ML?
> 
> No, this is the right list.
> 
> > Please point me out a place to look next with my problem.
> > 
> > I should have mentioned the kernel version and enclosure type:
> > # uname -a
> > Linux speicher48 2.6.31-17-server #54-Ubuntu SMP Thu Dec 10 18:06:56 UTC 2009 x86_64 GNU/Linux
> > # cat /sys/class/enclosure/10\:0\:24\:0/device/vendor 
> > CHENBRO 
> > # cat /sys/class/enclosure/10\:0\:24\:0/device/model 
> > SASX36 B0       
> 
> So the bug reports sound like something is going wrong in the device
> unbinding ... I don't see what from the code, so I need to play with an
> actual enclosure.  Unfortunately, that can only be done when physically
> present (unlike most of the SCSI development which I can do remotely),
> so it has to wait until I get back home.

is there some progress on this subject?
Just tell me if I can help anyhow.

Best regards
Lars

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

scsi device is not available in enclosure any more after hot plugging

[Lars Täuber]

Hi there!

One of my servers contains two scsi enclosures.
After hot removing a disk and hot adding another in the same slot the new disk gets assigned a device file but the enclosure (in sysfs) doesn't want to see it.

How can I force the enclosure to recognise the hot added disk.

Situation in sysfs:
# ls -l "/sys/class/enclosure/10:0:24:0/SLOT 010"
insgesamt 0
-rw-r--r-- 1 root root 4096 2010-01-15 14:30 active
lrwxrwxrwx 1 root root 0 2010-01-15 12:56 device -> ../../../../../../../port-10:0:11/end_device-10:0:11/target10:0:10/10:0:10:0
-rw-r--r-- 1 root root 4096 2010-01-15 14:31 fault
-rw-r--r-- 1 root root 4096 2010-01-15 14:40 locate
drwxr-xr-x 2 root root 0 2010-01-15 14:01 power
-rw-r--r-- 1 root root 4096 2010-01-15 14:01 status
-r--r--r-- 1 root root 4096 2010-01-15 14:01 type
-rw-r--r-- 1 root root 4096 2010-01-15 14:01 uevent

The link «device» is dead after hot removing the device and keeps vanished after hot adding the new device.
The hot added device gets assigned a device file and it is reachable.
Even
# echo 1 > /sys/bus/scsi/devices/10\:0\:24\:0/rescan
doesn't change anything.

How can I force the link to be updated towards
-> ../../../../../../../port-10:0:26/end_device-10:0:26/target10:0:25/10:0:25:0
???


Is there a detailed description of the sysfs regarding scsi on the web?

Thanks
Lars

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html