[mdlug] Drive Assignment Changed when Reinserted into Server

[Wojtak, Greg (Superfly)]

You could alternately use LVM which doesn't care about /dev/sd* entries.
UUID and LVM
both abstract it enough so you don't have to worry about changing letters
on the dev
entries.  As far as running out of drive letters - I *think* once you
exceed 26 drives, 
then you start in at double letters, I believe (/dev/sdaa).  I may be
mistaken though.

Greg Wojtak
Sr. Unix Systems Engineer
Office: (313) 373-4306
Cell: (734) 718-8472





On 2012-07-01 3:09 PM, "Jeff Hanson" <jhansonxi at gmail.com> wrote:

>On Sun, Jul 1, 2012 at 2:35 PM, Robert Adkins II <radkins at impelind.com>
>wrote:
>> When I pulled the drive, it was listed as /dev/sdh and when it was
>> reinserted and "automatically" recognized by the hardware the drive was
>> assigned to /dev/sdi.
>>
>> I am unsure if this will prove to be an issue down the road where the
>>system
>> will "run" out of /dev/sd* assignments or if there is something that I
>>can
>> or should have done to flush the old /dev/sdh so that the next inserted
>> drive would take the /dev/sdh spot when inserted.
>>
>
>Assuming that the kernel isn't reserving sdh due to a bad disconnect,
>you can use UUIDs in fstab to specify specific drives.  See the
>"blkid" command.
>_______________________________________________
>mdlug mailing list
>mdlug at mdlug.org
>http://mdlug.org/mailman/listinfo/mdlug