Hi Shivakumar, The fact that /var/run/nodelist is not generated on a reboot suggests something is not working correctly on the SunCluster side. The SunCluster framework is responsible for generating /var/run/nodelist and SVM depends on that file to figure out active diskset owners (the default owner is the first host in the diskset). Do you have or the correct SunCluster packages for multi-owner diskset installed? I can't remember the packages names but there are specific packages for multi-owner disksets.
-tony Shivakumar GN wrote: > Dear Group members, > > In a cluster system with solaris volume manager setup, the system is fine > till the first restart. On restart, the multi-owner information is getting > lost. Also one of the nodes is no longer identified as a member of the > diskset. > (/var/run/nodelist was manually created and is not persistent across reboots). > > Can someone let me know how to ensure multi-ownership and membership > information is maintained even on reboot? I had posted a related item > earlier, but I didn't have info regarding the history of the system since it > had passed couple of hands before I got it. Now, the system has been setup > from scratch. > > Details of the steps performed are provided below: > ------------------------------------------------------- > After OS+Cluster setup+Oracle rac patch, the following operations were > performed. > 1. Create /var/run/nodelist with the below entries on both host1 and host2 > 1 host1 <host1-ip> > 2 host2 <host2-ip> > 2. Create multiowner disksets (on host1) > metaset -s oradg -M -a -h host1 host2 > 3. Add global devices to the disk set (on host1) > metaset -s oradg -a /dev/did/rdsk/d1 /dev/did/rdsk/d4 /dev/did/rdsk/d2 > /dev/did/rdsk/d5 > 4. Ownership on as seen from both host1 and host2 are as below > > # metaset -s oradg > Multi-owner Set name = oradg, Set number = 1, Master = host1 > Host Owner Member > host1 multi-owner Yes > host2 multi-owner Yes > > Driv Dbase > d1 Yes > d4 Yes > d2 Yes > d5 Yes > > 5. Reboot the system (host1 & then host2) > 6. Now the diskset is no longer recognised as multi-owner. Also host2 is no > longer a member as seen from outputs of below commands. > > root at host1 # scstat -D > Device Group Online Status > ------------ ------------- > Multi-owner device group: oradg - > > > root at host1 # metaset -s oradg > > Multi-owner Set name = oradg, Set number = 1, Master = host1 > Host Owner Member > host1 Yes > host2 No > > Driv Dbase > d1 Yes > d4 Yes > d2 Yes > d5 Yes > > > 9. Now create /var/run/nodelist on both nodes as before and attempt to join > the nodes into ownership list. host2 fails to join :( > > root at host1 # metaset -s oradg -j > root at host2 # metaset -s oradg -j > metaset: host2: oradg: node host2 is not in membership list > > root at host2 # metaset -s oradg > > Multi-owner Set name = oradg, Set number = 1, Master = > Master and owner information unavailable until joined (metaset -j) > > Host Owner Member > host1 multi-owner Yes > host2 No > > Driv Dbase > d1 Yes > d4 Yes > d2 Yes > d5 Yes > > root at host2 # /usr/cluster/bin/scconf -pvv | grep oradg > Device group name: oradg > (oradg) Device group type: Multi-owner_SVM > (oradg) Device group failback enabled: no > (oradg) Device group node list: host1, host2 > (oradg) Device group ordered node list: no > (oradg) Device group desired number of secondaries: 0 > (oradg) Device group diskset name: oradg > > thanks in advance. > best regards > Shiv > > > This message posted from opensolaris.org > _______________________________________________ > lvm-discuss mailing list > lvm-discuss at opensolaris.org >
