Re: Ensuring SAN LUN persistent names after reboot...
- From: "Sandor W. Sklar" <ssklar@xxxxxxxxxxxx>
- Date: Thu, 1 Nov 2007 15:07:49 -0700
On Nov 1, 2007, at 2:22 PM, Arpotu wrote:
Hello,
I have yet another SAN migration question. We're going to add many new
SAN LUNs, which will end up being /dev/sdp-/dev/sdas. Once the new
storage is built as md devices and added to LVM, we are going to release
the old /dev/sdb-/dev/sdo devices.
My concern is that after a reboot, the new devices will rename themselves
to /dev/sdb-/dev/sdae and it will break the md device pairing (and LVM).
Is there any way to ensure that LUN names are persistent after a reboot?
http://kbase.redhat.com/faq/FAQ_85_8082.shtm
... use UUIDs to refer to the disks, instead of the /dev/sdX devices.
(As an aside, maybe I'm stupid, but I find that SAN storage is so much more complicated and fragile on Linux then on Solaris or AIX.)
-s-
--
Sandor W. Sklar, Unix Systems Administrator
Stanford University Libraries & Academic Information Resources (SULAIR)
http://library.stanford.edu
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
- Follow-Ups:
- References:
- Ensuring SAN LUN persistent names after reboot...
- From: Arpotu
- Ensuring SAN LUN persistent names after reboot...
- Prev by Date: Re: Ensuring SAN LUN persistent names after reboot...
- Next by Date: Re: Ensuring SAN LUN persistent names after reboot...
- Previous by thread: Re: Ensuring SAN LUN persistent names after reboot...
- Next by thread: Re: Ensuring SAN LUN persistent names after reboot...
- Index(es):
Relevant Pages
|
