if you do this on ASM disks or gpfs disks you are wiping the header. The device will stay up til your next reboot and be beautiful and clean after the reboot so this is a terrible idea.
You do get an output from the commands I listed even with ASM devices and GPFS disks and even from completely unassigned open disks. It might be a cryptic unreadable output but it is an output. If you get nothing or a one-line-error the disks are not open.
But maybe I have a different understanding what open means. Are you trying to find out if the disks are unused? Are you using AIX mpio or any kind of multipathing software? With ASM, before you make ANY changes to the disks, ask the DBAs to backup the disk headers. Strictly speaking by design, AIX has no idea if the disks are used or not - but oracle will hold a lock on them while still allocated - which is a curse and a blessing for above reason - you will STILL wipe the header. For gpfs, the cluster itself should be able to tell you which disks it is using - try
command. For normal disks in VGs, a simple
will tell you which disks are not in use from LVM perspective.
Hi i need help pls ...
Server type sun fire 3800 I need to install solaris 9 .
When i boot the system i recieve the following :
System Controller 'sunfire3800':
Type 0 for Platform Shell
Type 1 for domain A console
Type 2 for domain B console
Type 3 for... (5 Replies)
I have a real emergency. I have a Sun Fire V240 UltraSparc server and am connected via the Serial Mgmnt Port with a Laptop. I have been building an Oracle database on it for the past couple months, not getting very far along with it , when suddenly, the system had a fatal crash. I've lost the... (2 Replies)
I've a Sun V440 machine, and it's running solaris 10 .. for some reason i need to install a fresh copy of solaris 10. for that i've prepared solaris 10 dvd but surprisingly i found there is no any dvd rom on this machine, so i've took a dvd rom from a V240 machine and inserted on V440.
after... (3 Replies)
Hi guys,
I had a solaris box, with veritas controled disk.
1 disc is showing soft errors, how can I repair the soft errors?
Please help.
Cheers; (4 Replies)
Hi All,
Could anyone please help to resolve the below problem.
I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error.
I spent 2 days for the above and go through with several suggestion found by googling. But no luck.
... (0 Replies)
Hi all,
I am not sure whether anyone of you using XIV to copy vg from one host to another. After I managed to copy all the respective vg over to destination vg, and map all vg to destination and when come to varyonvg, I got the following error
0516-510 varyonvg: Physical volume not found for... (2 Replies)
I installed a new hard drive completely blank.
sun blade 150
openboot 4.10.6
message:
Boot device: disk:a File and args:
Bad magic number in disk label
Can't open label package
Evaluating:
Can't open boot device (15 Replies)
Hello Forum,
I'm really in a fix now,
I'm getting this error message now, seems like the boot block is damaged?
When I do probe-all the system freezes...
Can any one guide me as what to do next?
System is Solaris 8 running Open Boot PROM 4
System also does not have a cd/dvd rom drive...
... (17 Replies)
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
LEARN ABOUT SUNOS
metaimport
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)