Disk Suite - metainit failing
I'm trying to set up Solstice DiskSuite on an Ultra30 Running Solaris 8.
I have two 4.3GB disks set up as follows
c0t0d0s0 = /
c0t0d0s6 = /export/home
c0t0d0s7 = unassigned - to be used for state database replicas
c0t1d0s5 = /export/home0
c0t1d0s6 = unassigned for the moment but will be used to mirror root
c0t1d0s7 = unassigned - to be used for state database replicas
I've used metadb to set up state database replicas on c0t1d0s7 and c0t0d0s7. metadb -i reports that these seem to be OK.
I'd like to mirror root but when I try
metainit -f d1 1 1 c0t0d0s0
I get
metainit: U30: d1: No such file or directory
(U30 is the hostname of my Ultra30)
Any ideas as to which file or directory is missing or what else might be preventing me from creating d1
Thanks & regards
[877 byte] By [
Kevin_N] at [2007-11-25 23:38:47]
# 3
Sorry to have taken so long to respond on this.
Annual Hols, Christmas hols and restricted access to the test machine have all conspired against me :-)
After running metadb to create the state databases metastat showed nothing
After trying (and failing) to run metainit - metastat still showed nothing
However I have now managed to solve the problem
By "truss"ing the attempt to run metainit I could see that the system was trying and failing to access /dev/md/rdsk/d1 - 'cos it didn't exist. I thought that this would be created by metainit, but looking at a second Solaris box all the possible /dev/md/rdsk/dX entries were already present and symlinked to entries in /devices.
The reason the entries in /dev/md/rdsk on my first box were missing was that /etc/devlink.tab was corrupt & unreadable so the reconfigure re-boot wasn't creating the correct links.
Copying /etc/devlink.tab from my second Solaris box seems to have sorted the system out & I now have a happy DiskSuite Installation
Is the copying of devlink.tab from a second machine likely to have any unexpected side-effects?
Many thanks for the help folks
Regards
Kevin
