Thank you all for the replies! The problem was not in metadb but in the BigBrother monitoring script that was accepting good line only the ones containing the following strings 'flags|ampluo|apluo'. The fix was to grep out all upper case flags (because the upper case flags are negative flags) and keep the only the lower case flags. The "p", "l" and "o" flags will show only after a reboot but because the data replication is working well there is no reason to reboot the server only for that. Thank you again, Radu On Thursday 25 August 2005 14:54, you wrote: > I just ran a quick test and added 2 new replicas to a test system I have. > Their status shows up as "u" only and metatool reports all is good with > the database. > After reboot all replicas showed "luo". > > I would check the settings on Big Brother (I've never used it, so I don't > know how the config is put together) and see if you can't arrange it to > just check for "u" on all the replicas and "l", "o" on at least one > replica. > > > --CHRis > > Chris H. Ruhnke > Technical Services Professional > IBM Global Services > Dallas, TX > > > O'Toole's Law: Murphy is an optimist. > > > > RoLinux <rolinux@online.ie> > 08/25/2005 08:14 AM > > To > Chris Ruhnke/St Louis/IBM@IBMUS > cc > > Subject > Re: metadb question (flags missing) > > > > > > > > Hi Chris, > Thank you for the reply. > > I don't know enough about metadb and solaris but we use BigBrother and > this tool is still showing red until is not able to find the "apluo" > flags. > So do you recon I will be able to get back the P L O flags only by > rebooting? > > Thank you, > Radu > > > > On Thursday 25 August 2005 12:11, you wrote: > > I am by no means a SDS guru, but I did sleep at a Holiday Inn Express > last > > night... > > > > Why do you think you need the "l" and "o" flags set? > > > > Certainly "o" will NOT be set. This flag mean that the replica was > active > > before the last mddb configuration change. > > When you replaced the harddrive and recreated the state replicas on that > > > drive you performed a config change. > > > > "l" means the locator for the replica was read successfully. This flag > > will probably not be set until your next reboot. > > I would expect that the locator does not need to be read when you create > a > > replica. > > > > > > --CHRis > > > > Chris H. Ruhnke > > Technical Services Professional > > IBM Global Services > > Dallas, TX > > > > > > O'Toole's Law: Murphy is an optimist. > > > > > > > > RoLinux <rolinux@online.ie> > > Sent by: sunmanagers-bounces@sunmanagers.org > > 08/25/2005 04:50 AM > > > > To > > sunmanagers@sunmanagers.org > > cc > > > > Subject > > metadb question (flags missing) > > > > > > > > > > > > > > Hi > > We had a failure on a raid 1 software configuration on a Netra t1. > > We changed the hard drive, done the repartition, used metareplace, used > > "metadb -d" and "metadb -c 2 -a" > > but the metadb is not showing the correct info (we need the L and O > flags > > for the second hard disk). > > > > AVAILABLE DISK SELECTIONS: > > 0. c0t0d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248> > > /pci@1f,0/pci@1,1/scsi@2/sd@0,0 > > 1. c0t1d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248> > > /pci@1f,0/pci@1,1/scsi@2/sd@1,0 > > > > > > Before failure the metadb and metastat output (from BigBrother) was: > > > > flags first blk block count > > a m p luo 16 1034 > > /dev/dsk/c0t0d0s3 > > a p luo 1050 1034 > > /dev/dsk/c0t0d0s3 > > a p luo 16 1034 > > /dev/dsk/c0t1d0s3 > > a p luo 1050 1034 > > /dev/dsk/c0t1d0s3 > > > > d10: Mirror > > d11: Submirror of d10 > > Device Start Dbase State Hot Spare Time > > c0t0d0s0 0 No Okay Wed Sep 20 > 00:43:45 > > 2000 > > d12: Submirror of d10 > > Device Start Dbase State Hot Spare Time > > c0t1d0s0 0 No Okay Wed Sep 20 > 00:43:56 > > 2000 > > d20: Mirror > > d21: Submirror of d20 > > Device Start Dbase State Hot Spare Time > > c0t0d0s1 0 No Okay Wed Sep 20 > 01:06:16 > > 2000 > > d22: Submirror of d20 > > Device Start Dbase State Hot Spare Time > > c0t1d0s1 0 No Okay Wed Sep 20 > 01:06:26 > > 2000 > > d60: Mirror > > d61: Submirror of d60 > > Device Start Dbase State Hot Spare Time > > c0t0d0s5 0 No Okay Wed Sep 20 > 01:06:54 > > 2000 > > d62: Submirror of d60 > > Device Start Dbase State Hot Spare Time > > c0t1d0s5 0 No Okay Wed Sep 20 > 01:07:10 > > 2000 > > > > > > After the replacement the metadb and metastat output (from BigBrother) > is: > > > > flags first blk block count > > a m p luo 16 1034 > > /dev/dsk/c0t0d0s3 > > a p luo 1050 1034 > > /dev/dsk/c0t0d0s3 > > a u 16 1034 > > /dev/dsk/c0t1d0s3 > > a u 1050 1034 > > /dev/dsk/c0t1d0s3 > > > > d10: Mirror > > d11: Submirror of d10 > > Device Start Dbase State Hot Spare Time > > c0t0d0s0 0 No Okay Wed Sep 20 > 00:43:45 > > 2000 > > d12: Submirror of d10 > > Device Start Dbase State Hot Spare Time > > c0t1d0s0 0 No Okay Wed Aug 03 > 18:15:17 > > 2005 > > d20: Mirror > > d21: Submirror of d20 > > Device Start Dbase State Hot Spare Time > > c0t0d0s1 0 No Okay Wed Sep 20 > 01:06:16 > > 2000 > > d22: Submirror of d20 > > Device Start Dbase State Hot Spare Time > > c0t1d0s1 0 No Okay Wed Aug 03 > 17:45:39 > > 2005 > > d60: Mirror > > d61: Submirror of d60 > > Device Start Dbase State Hot Spare Time > > c0t0d0s5 0 No Okay Wed Sep 20 > 01:06:54 > > 2000 > > d62: Submirror of d60 > > Device Start Dbase State Hot Spare Time > > c0t1d0s5 0 No Okay Wed Aug 03 > 17:29:57 > > 2005 > > > > > > We are missing the L and O flags on the second hard drive. > > > > Can you please help me understand what steps have to be done to solve > the > > problem? > > > > Thank you, > > Radu > > _______________________________________________ > > sunmanagers mailing list > > sunmanagers@sunmanagers.org > > http://www.sunmanagers.org/mailman/listinfo/sunmanagers _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Thu Aug 25 11:36:23 2005
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:51 EST