This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C2B7F9.A31669D0
Content-Type: text/plain;
charset="iso-8859-1"
I think you got it. To force the order I can only think of two ways:
1. recreate the sym-links in /dev/rmt ..or..
2. add the drives one-at-a-time and do your discovery after each.
-M
-----Original Message-----
From: Shafto, Eric [mailto:Eric.Shafto AT DrKW DOT com]
Sent: Thursday, January 09, 2003 6:08 AM
To: 'veritas-bu AT jasons DOT us'; Donaldson, Mark
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Procedure for creating /dev/rmt devices
Thanks to you and to Mark for your replies. Unfortunately, I was not
explicit enough (again!) in my message.
Well, third time's the charm:
I need the drives to be recognized in a particular order. I've done this in
the past by tweaking lots of config files, and it was working until we added
some more drives. At that point everything went to heck, and as someone on
the list pointed out, cross-referenced drives can ruin your whole day.
Not having the time to mess with the config files, I fixed it by deleting
and manually recreating all 120 or so /dev/rmt links (for i in "" b bn c cb
cbn ....). Not terribly painful, but not terribly stable either. If I were
to delete /dev/rmt and do a devfsadm again, I know it'd mess me up.
I have some more hardware to add, and a three-day weekend coming up, so I'd
like to do it right. My documentation from the first experience is a little
hazy (trying to remember exactly what I did after a two-day high-stress
marathon), and I was hoping someone who had been through this might have a
clearer explanation of what files needed to be tweaked and how.
Thanks again for your patience, and thanks in advance for any assistance you
may be able to render.
-----Original Message-----
From: veritas-bu AT jasons DOT us [mailto:veritas-bu AT jasons DOT us]
Sent: Wednesday, January 08, 2003 4:44 PM
To: Donaldson, Mark
Cc: Shafto, Eric; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Procedure for creating /dev/rmt devices
On Wed, 8 Jan 2003, Donaldson, Mark wrote:
> If they're visible as targets then a simple reconfig reboot should handle
> it. Either touch "/reconfigure" and reboot our "boot -r" from the BIOS
> prompt.
Similarly "reboot -- -r" (yes, you need all three dashes) will do the same
thing with a single command.
> You can check the drive visibility with "sgscan tape" beforehand or with a
> "probe-scsi-all" at the BIOS prompt.
>
> Yet another alternative is to run:
> "drvconfig && devlinks && disks && ports && tapes" as root on the cmd line
> and it'll emulate the reconfigure boot - although experience tells me that
> this sometimes locks up in high lun-count systems.
With Solaris 2.7 and later you can use "devfsadm" instead of the string of
commands listed above. And as Mark mentioned it can lock or appear to
hang the machine if you have a large number LUNs but otherwise it should
be fine. I've done this on systems with 10 SAN drive volumes mounted
without a problem. Just have patience. The command can take several
minutes to complete.
> Make sure to use persistent addressing in your SAN scheme - you don't want
> these addresses moving about.
I'll second that. Cross-crossed drives can wreck your day.
-Jason
-----
Jason K. Schechner - check out www.cauce.org and help ban spam-mail.
=The difference between genius and stupidity is that genius has bounds.=
---There is no TRUTH. There is no REALITY. There is no CONSISTENCY.---
---There are no ABSOLUTE STATEMENTS I'm very probably wrong.---
If you have received this e-mail in error or wish to read our e-mail
disclaimer statement and monitoring policy, please refer to
http://www.drkw.com/disc/email/ or contact the sender.
------_=_NextPart_001_01C2B7F9.A31669D0
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>RE: [Veritas-bu] Procedure for creating /dev/rmt devices</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>I think you got it. To force the order I can only think
of two ways:</FONT>
<BR><FONT SIZE=2>1. recreate the sym-links in /dev/rmt ..or..</FONT>
<BR><FONT SIZE=2>2. add the drives one-at-a-time and do your discovery after
each.</FONT>
</P>
<P><FONT SIZE=2>-M</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Shafto, Eric [<A HREF="mailto:Eric.Shafto AT DrKW DOT
com">mailto:Eric.Shafto AT DrKW DOT com</A>]</FONT>
<BR><FONT SIZE=2>Sent: Thursday, January 09, 2003 6:08 AM</FONT>
<BR><FONT SIZE=2>To: 'veritas-bu AT jasons DOT us'; Donaldson, Mark</FONT>
<BR><FONT SIZE=2>Cc: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=2>Subject: RE: [Veritas-bu] Procedure for creating /dev/rmt
devices</FONT>
</P>
<BR>
<P><FONT SIZE=2>Thanks to you and to Mark for your replies. Unfortunately, I
was not</FONT>
<BR><FONT SIZE=2>explicit enough (again!) in my message.</FONT>
</P>
<P><FONT SIZE=2>Well, third time's the charm:</FONT>
</P>
<P><FONT SIZE=2>I need the drives to be recognized in a particular order. I've
done this in</FONT>
<BR><FONT SIZE=2>the past by tweaking lots of config files, and it was working
until we added</FONT>
<BR><FONT SIZE=2>some more drives. At that point everything went to heck, and
as someone on</FONT>
<BR><FONT SIZE=2>the list pointed out, cross-referenced drives can ruin your
whole day.</FONT>
</P>
<P><FONT SIZE=2>Not having the time to mess with the config files, I fixed it
by deleting</FONT>
<BR><FONT SIZE=2>and manually recreating all 120 or so /dev/rmt links (for i in
"" b bn c cb</FONT>
<BR><FONT SIZE=2>cbn ....). Not terribly painful, but not terribly stable
either. If I were</FONT>
<BR><FONT SIZE=2>to delete /dev/rmt and do a devfsadm again, I know it'd mess
me up.</FONT>
</P>
<P><FONT SIZE=2>I have some more hardware to add, and a three-day weekend
coming up, so I'd</FONT>
<BR><FONT SIZE=2>like to do it right. My documentation from the first
experience is a little</FONT>
<BR><FONT SIZE=2>hazy (trying to remember exactly what I did after a two-day
high-stress</FONT>
<BR><FONT SIZE=2>marathon), and I was hoping someone who had been through this
might have a</FONT>
<BR><FONT SIZE=2>clearer explanation of what files needed to be tweaked and
how.</FONT>
</P>
<P><FONT SIZE=2>Thanks again for your patience, and thanks in advance for any
assistance you</FONT>
<BR><FONT SIZE=2>may be able to render.</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: veritas-bu AT jasons DOT us [<A HREF="mailto:veritas-bu
AT jasons DOT us">mailto:veritas-bu AT jasons DOT us</A>]</FONT>
<BR><FONT SIZE=2>Sent: Wednesday, January 08, 2003 4:44 PM</FONT>
<BR><FONT SIZE=2>To: Donaldson, Mark</FONT>
<BR><FONT SIZE=2>Cc: Shafto, Eric; veritas-bu AT mailman.eng.auburn DOT
edu</FONT>
<BR><FONT SIZE=2>Subject: RE: [Veritas-bu] Procedure for creating /dev/rmt
devices</FONT>
</P>
<BR>
<P><FONT SIZE=2>On Wed, 8 Jan 2003, Donaldson, Mark wrote:</FONT>
</P>
<P><FONT SIZE=2>> If they're visible as targets then a simple reconfig
reboot should handle</FONT>
<BR><FONT SIZE=2>> it. Either touch "/reconfigure" and
reboot our "boot -r" from the BIOS</FONT>
<BR><FONT SIZE=2>> prompt.</FONT>
</P>
<P><FONT SIZE=2>Similarly "reboot -- -r" (yes, you need all three
dashes) will do the same</FONT>
<BR><FONT SIZE=2>thing with a single command.</FONT>
</P>
<P><FONT SIZE=2>> You can check the drive visibility with "sgscan
tape" beforehand or with a</FONT>
<BR><FONT SIZE=2>> "probe-scsi-all" at the BIOS prompt.</FONT>
<BR><FONT SIZE=2>></FONT>
<BR><FONT SIZE=2>> Yet another alternative is to run:</FONT>
<BR><FONT SIZE=2>> "drvconfig && devlinks && disks
&& ports && tapes" as root on the cmd line</FONT>
<BR><FONT SIZE=2>> and it'll emulate the reconfigure boot - although
experience tells me that</FONT>
<BR><FONT SIZE=2>> this sometimes locks up in high lun-count systems.</FONT>
</P>
<P><FONT SIZE=2>With Solaris 2.7 and later you can use "devfsadm"
instead of the string of</FONT>
<BR><FONT SIZE=2>commands listed above. And as Mark mentioned it can lock
or appear to</FONT>
<BR><FONT SIZE=2>hang the machine if you have a large number LUNs but otherwise
it should</FONT>
<BR><FONT SIZE=2>be fine. I've done this on systems with 10 SAN drive
volumes mounted</FONT>
<BR><FONT SIZE=2>without a problem. Just have patience. The command
can take several</FONT>
<BR><FONT SIZE=2>minutes to complete.</FONT>
</P>
<P><FONT SIZE=2>> Make sure to use persistent addressing in your SAN scheme
- you don't want</FONT>
<BR><FONT SIZE=2>> these addresses moving about.</FONT>
</P>
<P><FONT SIZE=2>I'll second that. Cross-crossed drives can wreck your
day.</FONT>
</P>
<P><FONT SIZE=2>-Jason</FONT>
</P>
<P><FONT SIZE=2>-----</FONT>
<BR><FONT SIZE=2>Jason K. Schechner - check out www.cauce.org
and help ban spam-mail.</FONT>
<BR><FONT SIZE=2>=The difference between genius and stupidity is that genius
has bounds.=</FONT>
<BR><FONT SIZE=2>---There is no TRUTH. There is no REALITY. There
is no CONSISTENCY.---</FONT>
<BR><FONT SIZE=2> ---There are no ABSOLUTE STATEMENTS
I'm very probably wrong.---</FONT>
</P>
<BR>
<P><FONT SIZE=2>If you have received this e-mail in error or wish to read our
e-mail disclaimer statement and monitoring policy, please refer to <A
HREF="http://www.drkw.com/disc/email/";
TARGET="_blank">http://www.drkw.com/disc/email/</A> or contact the
sender.</FONT></P>
</BODY>
</HTML>
------_=_NextPart_001_01C2B7F9.A31669D0--
|
