Sponsored Content
Full Discussion: DiskSuite dilemma
Operating Systems Solaris DiskSuite dilemma Post 302241852 by mgb on Tuesday 30th of September 2008 12:43:49 PM
Old 09-30-2008
DiskSuite dilemma

Hello,

We have this system a SunFire 280R running Solaris 8 Generic_117350-46. It has 2 36GB disks in it. They are mirrored with DiskSuite 4.2.1.

When we execute a metastat all the devices report an Okay status, but when we go into metatool everything is in the Critical (maintenance) state?

Can anyone explain this phenom or how to rectify it?

Thanks,

Mike
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

A Terminal Dilemma

Hi everyone, I hope this is the right place to ask this question... I have a contract to convert a mainframe/DB2 application to using AIX/Oracle. Everything went fine but we are now running into a terminal problem. With the Mainframe app, the clients had great response time from remote... (5 Replies)
Discussion started by: rocky_triton
5 Replies

2. Programming

dilemma in control flow

hello im facing a queer problem when i execute the foll code in unix # include <stdio.h> # include <unistd.h> main(int argc,char *argv) { FILE *fp = fopen("/ras/chirag/fifotest/file.fifo","a"); int i=1; fprintf(fp,argv); printf("I SLEEP"); system("date"); for (i=0;i<50;i++)... (2 Replies)
Discussion started by: tej.buch
2 Replies

3. What is on Your Mind?

Final Year Project dilemma

Hello everyone. Need some final year project ideas - what is actual/feasible and beneficial experience-wise? Preferably something related to Networking / Linux / UNIX / Security . Appreciate any help/idea. E.K. (0 Replies)
Discussion started by: reminiscent
0 Replies

4. Shell Programming and Scripting

dilemma what to use c++ or script for demon process

Hello all i need to implement demon that needs to extract data from db load the data to memory and according to this data to perform actions like sending emails or write/update files this action needs to be preformed each 30 min's now i really don't know what to decide or to compile c++... (5 Replies)
Discussion started by: umen
5 Replies

5. Red Hat

Patch management dilemma

I've inherited about 10 RHEL 3 boxes that are located in Europe behind a corporate firewall with no access to rhn.redhat.com I've been tasked with patching all of these systems but I ask, Does redhat issue patch bundles? In AIX, there are maintenance levels and Sun has patch clusters available... (4 Replies)
Discussion started by: Steelysteel
4 Replies

6. Solaris

disksuite mirroring d0 to d2 and d1 to d3

I have a SOlaris 10 v240 server. I'm installing disksuite to mirror the root drive D0 to D2. I also have one partition on disk 1 that I want to mirror to D3. I am not using ZFS right now. Can I add that to my initial mirroring configuration or can I only mirror 1 drive to 1 drive? Can I... (2 Replies)
Discussion started by: csross
2 Replies

7. Solaris

Disksuite question

Hello all, I have a Solaris Disksuite question :- I will be adding 4 new drives to an E250 server and need will be configuring 2 striped volumes each consisting 2 new disks with SVM. In the end i will have 2 volumes each of 72gb. So in effect i will have 1 volume called D7 and another volume... (6 Replies)
Discussion started by: commandline
6 Replies
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)
All times are GMT -4. The time now is 04:53 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy