Hey guys - I've been struggling all day with a problem that I can't
seem to get resolved. Even though I moved to Indy this summer, I must
say the CINLUG really lacks the active user base and definitely an
active mailing list, so I'm hoping one of you guys can give me a hand.
When we set up Oracle on a 3 node cluster with a SAN, our DBA assigned
the /dev/sd* devices to ASM (Oracle), not planning for possibility
that they could change in the future. Now we've another device to the
SAN and now we have the lovely behavior of /dev/sdb and /dev/sdc
belonging to the new SAN device LUNs, while all the older SAN LUNs
have been bumped up by 2 letters (old /dev/sdb is now /dev/sdd, old
/dev/sdc is now /dev/sde, etc.)
For the future, we'll use the WWN's to refer to the devices, but
considering that there are 64 drives on the older SAN, we really don't
want to go back and repoint all the volumes in Oracle.
I wrote a udev rule that seems to be running just fine as follows:
BUS=="scsi", SYSFS{vendor}=="TMS", SYSFS{model}=="RamSan",
PROGRAM=="/sbin/scsi_id -g -u -s /block/%k ",
RESULT=="20020c24000052434", NAME="ramsan"
The problem is that it creates the /dev/ramsan device I want, but I
still am stuck with a /dev/sdb that's tied to the same kernel device
(major/minor numbers).
Anyone have an idea what I'm doing wrong? This shouldn't matter much,
but this is a Red Hat Enterprise Linux 5.2 server. I know, I know,
it's not my favorite distro, either, but it's the only option if we
want support from IBM and Oracle. And, yes, I called Red Hat (and
suffered through about 20 minutes on hold, and that's "premium
support"), but they're supposed to "get back to me". The guy I was
talking to couldn't even spell my company's name right after about 3
attempts and explanations, so I'm not too hopeful about that avenue.
Thanks for any insight you can provide.
Jeremy
_______________________________________________
Fwlug mailing list
[email protected]
http://fortwaynelug.org/mailman/listinfo/fwlug_fortwaynelug.org
