[mdlug] Drive Assignment Changed when Reinserted into Server

Tony Bemus tony at bemushosting.com
Mon Jul 2 11:16:31 EDT 2012


I always use the uuid and blkid method.

-----Original Message-----
From: Robert Adkins II <radkins at impelind.com>
Reply-to: MDLUG's Main discussion list <mdlug at mdlug.org>
To: 'MDLUG's Main discussion list' <mdlug at mdlug.org>
Subject: Re: [mdlug] Drive Assignment Changed when Reinserted into
Server
Date: Mon, 2 Jul 2012 10:38:51 -0400

Thanks for the extra information.

I want to eliminate potential issues before they become issues.

I'll review blkid and also LVM.

Still aiming for the goal of a good clean HD based backup system.

If worse comes to pass, I'll just leave two of the drives as "Hot Back Up"
drives and use a pair of USB to SATA Enclosures for the portable back up,
the USB system seems to be working significantly better with regards to
reconnecting a drive.

Regards,
Rob
 

> -----Original Message-----
> From: mdlug-bounces at mdlug.org 
> [mailto:mdlug-bounces at mdlug.org] On Behalf Of Wojtak, Greg (Superfly)
> Sent: Monday, July 02, 2012 10:08 AM
> To: MDLUG's Main discussion list
> Subject: Re: [mdlug] Drive Assignment Changed when Reinserted 
> into Server
> 
> 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
> 
> _______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug
> 

_______________________________________________
mdlug mailing list
mdlug at mdlug.org
http://mdlug.org/mailman/listinfo/mdlug

-- 
Tony Bemus
Bemus Hosting and Computer Repair
http://www.bemushosting.com





More information about the mdlug mailing list