Hi people,
I suppose I haven't been clear enough on my post.
I have a standalone raid sub-system, it presents it
self as a huge disk to a standard U/W scsi adapter.
I made further test with a spare disk and the advscan
worked ok. Specifically, I did :
# advscan -r dsk1
And the result was a domain called "domain_dsk1c" that
contained the file_set which I was able to mount just
by fixing the /etc/fstab file.
I belive the same thing applies to my raid sub-system.
Many thanks to all.
Zac
############ Answers I got #######################
FROM: alan_at_nabeth.cxo.dec.com
Assuming the RAID allows itself to be moved, the advscan
command you gave will do the desired things. This will
change the name of the domains based on the name of
the device, but that can probably be fixed easily enough.
FROM: Chuck Taylor <Chuck.Taylor_at_Vishay.com>
More information is needed to understand your
environment. Do both of your machines have identical
storage subsystems? Specifically, are you going to or
from an HSx based controller to or from a SCSI
interface adapter? At the AdvFS layer it looks like
you should be okay. But the lower layer may be a
problem if those lower level layers are different. Be
sure to do a vdump before you try to move the array -
just in case. You can always be sure to be able to
restore your system if you back it up first - assuming
that you get a good backup in the first place.
FROM: Nikola Milutinovic <Nikola.Milutinovic_at_ev.co.yu>
This is highly debatable. Contact your support first.
ORIGINAL POST
I will be moving a RAID array from a DEC 4100/DU 4.0D
to a DS10/Tru64 5.0. The raid is running AdvFS.
I read the man page for advscan and it looks like
advscan -r dsk? ( ? = 1,2,3 or wherever the disk appears)
will re-create the domains and make the file_sets available
for mounting.
Is this all there is to it or I am missing some little trick?
Also, are both 4.0D and 5.0 AdvFS compatible ?
Received on Thu Nov 18 1999 - 16:14:08 NZDT