Hi, I replaced one faulty disk with a new disk in the same disk slot. The faulty disk has a device name as c2t6d0. I expect the system would use the same device name for the new disk. However, it did not. Instead, the system uses c2t14d0, which is next free available device name, for the new disk. Is this epxected? If I want to use the same device name, should I first unconfigure the device and then reconfigure it after replacing faulty disk? Is assigning device controllable? I am running Solaris 10 U7. Appreicate your help. Simon -- This message posted from opensolaris.org
On 18/06/10 09:00 AM, Simon Gao wrote:> Hi, > > I replaced one faulty disk with a new disk in the same disk slot. The > faulty disk has a device name as c2t6d0. I expect the system would use > the same device name for the new disk. However, it did not. Instead, > the system uses c2t14d0, which is next free available device name, for > the new disk. Is this epxected? > > If I want to use the same device name, should I first unconfigure the > device and then reconfigure it after replacing faulty disk? Is > assigning device controllable? > > I am running Solaris 10 U7.Is this device attached to an mpt controller? If so, then mpt''s firmware (not the driver) will assign a new target id to the device that you replaced, and will keep doing so until you get to (iirc) 120. So yes, what you saw is expected. Assuming this is an mpt-attached device, then you won''t be able to use the same cXtYdZ name as the old device. It really shouldn''t be a problem for you. James C. McPherson -- Senior Software Engineer, Solaris Oracle http://www.jmcp.homeunix.com/blog
Thanks James. Yes. The controller is LSI Logic SAS1068E. When device name changed, the following command as described by ZFS documentation will fail: zpool replace mypool <old_disk_name> Instead one must use: zpool replace mypool <old_disk_name> <new_disk_name> ZFS document says if replacing disk is inserted into the same slot position, only former command is needed. This is not true in my case. The document should give warning or list exception such as this case. Again thanks for your help. Simon -- This message posted from opensolaris.org
> Hi, > > I replaced one faulty disk with a new disk in the > same disk slot. The faulty disk has a device name as > c2t6d0. I expect the system would use the same device > name for the new disk. However, it did not. Instead, > the system uses c2t14d0, which is next free available > device name, for the new disk. Is this epxected? > > If I want to use the same device name, should I first > unconfigure the device and then reconfigure it after > replacing faulty disk? Is assigning device > controllable? > > I am running Solaris 10 U7. > > Appreicate your help. > > SimonSince you are running an LSI hba per your later posts you might want to check out this earlier thread: http://opensolaris.org/jive/message.jspa?messageID=184811 Which discusses the use of lsiutil to disable this "reordering" or persistent mapping of drives. -- This message posted from opensolaris.org