Hi All.
Been out of Unix admin work for about 10 years and I just took over a new position...
seeing the 'use metadb to delete databases which are broken message' on reboot. The system comes up but I'm not sure what's on this disk that's failing...
metadb -i shows:
Code:
excalibur# metadb -i
flags first blk block count
a m pc luo 16 1034 /dev/dsk/c0t2d0s3
M pc unknown unknown /dev/dsk/c3t0d0s3
a pc luo 16 1034 /dev/dsk/c0t1d0s3
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
Can I just delete it and re-attach (metadb -d and -a options)?
Just need some assistance on determining if this necessary or being used at all.
Disksuite needs a minimum of 3 metastate databases therefore when setting thing up I run something like:
Code:
# metadb -a -f -c 3 c0t0d0s7 c0t1d0s3 c1t0d0s7
This makes 3 copies of the metastate database in each slice so that I have a few to spare and even with only one out of the three disks working DiskSuite still works.
If you have another disk with some free space then make a small slice on it (the minimum last time I tried was about 40MB, plenty of room) add another metastate database (3 copies!) onto it, then remove the problematic one, newfs(1) the slice that had the erroneous metastate database in it to wipe it and then try recreating it again.
Hi,
I have inherited a system with two disks mirrored, and only 1 metadb on each, I have deleted the db on c1t1 and recreated 3 which is fine.
But when it comes to c1t0, the metadb -d /dev/dsk/c1t0d0s5 doesnt removed the existing db and the create metadb -a -f -c3 /dev/dsk/c1t0dos5 wont... (0 Replies)
hi all , i need please help with this command i tried to create a metadb in live system , i got this message metadb: fintest: c0t0d0s7: overlaps with c0t0d0s0 which is mounted as '/'
any idea of who to do the creation with such problem (3 Replies)
Hi, my root pool is as follows. How can I create a metadb if I want to create SVM volumes?
zpool status
pool: rpool1
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
rpool1 ONLINE 0 0 0
c4t1d0s0 ... (10 Replies)
When I was trying to mirror in my v880 server after OS up gradation from 8 to 10
metadb -afc 3 /dev/dsk/c1t1d0s7
I got an error
metadb: Segmentation Fault
Segmentation Fault (core dumped)
Then I logged a case to Oracle/sun team they suggest
"Please could you try
metadb -ac 3... (0 Replies)
Hi All,
I have two disks which has been configured for RAID 1 Already.
I am adding more 6 disks in the system and I am configuring RAID 1 for all.
So in this case should , how should i create a metadb .
Thanks and Regards
Rj (3 Replies)
Hi All,
I have to do disk mirroring, for that I have to create a metadb as disk mirroring have to do with SVM. However I do not have any slice free for metadb.
What are the options? Please suggest (4 Replies)
Hi All,
Please help me on metastat and metadb. I don't where do start on doing queries on all these solaris 8 disk. Give me an idea and I will do the rest?
What's the command for verifying raid 1 or 5? Verify what's the adapter (scsi or san)?
Thanks in advance,
itik (5 Replies)
