Solaris 10 and SVM Disk Sets

From: Dale Ghent (daleg@elemental.org)
Date: Mon Apr 18 2005 - 15:28:42 EDT


I'm busy attempting to create a shared (not multi-owner) disk set on
Solaris 10 x86.

I create the disk set on the "master" server and then add disks to it:

[root@hfs10]~>metaset -s afs-hfs10 -a
c4t600039300001034A01000000D5BF8AEEd0
c4t600039300001057C01000000D5D0DB4Ad0

And it looks right:

[root@hfs10]~>metaset -s afs-hfs10
Set name = afs-hfs10, Set number = 1

Host Owner
   hfs10.afs Yes

Drive Dbase

/dev/dsk/c4t600039300001034A01000000D5BF8AEEd0 Yes

/dev/dsk/c4t600039300001057C01000000D5D0DB4Ad0 Yes

So then I try to add the second host to the disk set and get an error:

[root@hfs10]~>metaset -s afs-hfs10 -a -h hfs11.afs
metaset: hfs11.afs: rpc.metad: No such file or directory

rpc.metad is running on both hosts, and a truss and snoop of both don't
seem to indicate that one is trying to open or write to a file that the
process doesn't have permission to. Root is indeed a member of GID 14
as the SVM docs prescribe. Google and the Sun search results don't seem
to shed any detail on what may be causing this. There is no network
filtering going on or anything.

On the hfs11.afs box, if I monitor the contents of /dev/md, a afs-hfs10
symlink shows up pointing to shared/1, but shared/1 is never created.
Right before I see the above error, the afs-hfs10 symlink is removed.

Any thoughts or experience with this?
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:30:33 EDT