Metadb


 
Thread Tools Search this Thread
Operating Systems Solaris Metadb
# 1  
Old 03-30-2012
Metadb

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 create more.

Please advise, many thanks in advance.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Solaris can not boot because metadb lost

how to recovery metadb? Thanks! (1 Reply)
Discussion started by: dzung
1 Replies

2. Shell Programming and Scripting

Creating metadb

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)
Discussion started by: semaan
3 Replies

3. Solaris

How to create metadb with zpool in Solaris 11

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)
Discussion started by: incredible
10 Replies

4. Solaris

Meta Devices ( Metadb )

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)
Discussion started by: jegaraman
3 Replies

5. Solaris

Creating MetaDB

I'm trying create metadb's. I'm telling them to live on mounted partitions. Is this acceptable? (3 Replies)
Discussion started by: adelsin
3 Replies

6. Solaris

metadb problem - server unable to boot

Hi everyone I have a problem. My configuration is as follows: Sun 280R server 2 x internal disks 3 x state databases on disk 1 3 x state databases on disk 2 Disk 1 was giving errors, so I cleared the mirrors on it, deleted the state databases and replaced the disk. Before attaching... (5 Replies)
Discussion started by: soliberus
5 Replies

7. UNIX for Dummies Questions & Answers

metadb errors

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: excalibur# metadb... (1 Reply)
Discussion started by: jamie_collins
1 Replies

8. Solaris

How to create metadb when there is no free slice

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)
Discussion started by: kumarmani
4 Replies

9. Solaris

solaris with metadb

Hi All, If solaris has metadb services on the disk, it means that it has a HW raid controller. Or what. Thanks in advance. (1 Reply)
Discussion started by: itik
1 Replies

10. Solaris

help on metadb

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)
Discussion started by: itik
5 Replies
Login or Register to Ask a Question
metaimport(1M)															    metaimport(1M)

NAME
metaimport - imports disk sets into existing Solaris Volume Manager configurations SYNOPSIS
metaimport -s setname [-n] [-v] [-f] [disks...] metaimport -r [disks...] metaimport -V metaimport -? The metaimport command allows the importing of disk sets, including replicated disk sets, into an existing Solaris Volume Manager configu- ration. Replicated disk sets are disk sets created using remote replication software. The default Solaris Volume Manager configuration specifies a maximum number of disk sets that can be configured. The metaimport command fails if importing the disk set would result in exceeding the number of disk sets configured on the system. To increase the number of disk sets allowed on a system, see the . Use metaset(1M) or metastat(1M) to view the configuration of the imported set. You must run metaimport as root. metaimport requires a functional Solaris Volume Manager configuration before it runs. The following options are supported: -f Force the import, even if a quorum of replicas from the imported disk set is not available. This option could result in corrupt configurations and should only be used when metaimport fails with the "Insufficient quorum detected; exiting" error. If only a partial disk set is available, this option might be necessary to successfully import. Some or all data could be corrupted or unavailable when importing a partial set or a set lacking a replica quorum. -n Does not actually perform the operation, but shows the output or errors that would have resulted from the opera- tion, had it been run. -r Report on the non-configured disk sets found on the system. If no disk device or LUN is specified, metaimport reports on all non-configured disk sets attached to the system. When the name of one disk is specified, metaimport reports on the disk set (or virtual LUN) containing the specified disk. If two or more disks are specified, metaim- port reports on the set (or sets, if they belong to different disk sets) containing the specified disks. If two or more disks are specified, metaimport reports on the set (or sets, if they belong to different disk sets) containing the specified disks. -s setname Specify the disk set name to use when importing. The imported disk set will be called setname, without regard to the name it may have had on a different system. -v Verbose. Provides detailed information about the metadb replica location and status. -V Version information. -? Display a help message. Example 1: Importing a Disk Set The following example creates a disk set called blue and identifies c1t5d0 as a disk containing a state database replica from the disk set being imported. # metaimport -s blue c1t5d0 Example 2: Reporting Disk Sets to Import The following example scans all disks and LUNs attached to the system and configured as part of the system. It scans for disks that could be part of a disk set to be imported. Components that are already part of the Solaris Volume Manager configuration are ignored. This use of metaimport provides suggested forms of the metaimport command to use to actually import the disk sets that have been found. You can specify a component on the command line to reduce the scope of the scan and generate results more quickly. # metaimport -r 0 Successful completion. >0 An error occurred. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metareplace(1M), metaroot(1M), metaset(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), attributes(5) 16 May 2005 metaimport(1M)