Not what I wanted to hear, but I appreciate the answer :-( I will have to work a way round my specific issue. Thanks for the response. Simon. -----Original Message----- From: Kay Sievers [mailto:kay.sievers@xxxxxxxx] Sent: 19 November 2009 13:52 To: Simon Jackson Cc: linux-hotplug@xxxxxxxxxxxxxxx Subject: Re: SAS drive sysmlinks not recreated after hotplug removal and reinsertion. On Thu, Nov 19, 2009 at 14:35, Simon Jackson <sjackson@xxxxxxxxxxx> wrote: > It seems that path_id script is failing because after the unit is removed and inserted, a new SAS port number is allocated and path_id expects the sys_phy device to have the same number as the new port number. > > In the example I see, the original device was using port-0:2 and this is > corresponds to /sys/class/sas_phy/phy-0:2. > > When removed and replugged, the newly allocated port number is port-0:4 and the script is expecting this to correspond to /sys/class/sas_phy/phy-0:4 which does not exist as the initiator device is still /sys/class/sas_phy/phy-0:2. > > Can anyone tell me if there is a fix for this? Sorry, there is no fix available at the moment. More recent udev version have a C version of path_id, but SAS support is not implemented at all, because it was not working properly in the shell script. All the SAS stuff would need to be done from scratch for the current C program of path_id. Kay -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
