Hello,
Can somebody please help.
I'm able to view volume groups by using the command "lsvg", how can I view what space is available to that particular volume group
Many Thanks (3 Replies)
I have a Volume group on one of my production box. The no of PV's within the same is 16 which I need to increase.
How can this be done ?
Can this be done online or do we need a downtime for this ?
Please provide the exact details and steps for this activity urgently, as need to do this on my... (3 Replies)
Hello,
I have logical volume group of 50GB, in which I have 2 logical volumes, LogVol01 and LogVol02, both are of 10GB.
If I extend LogVol01 further by 10GB, then it keeps the extended copy after logical volume 2. I want to know where it keeps this information
Regards
Himanshu (3 Replies)
Hi Friends-
We know that the Max PP size in a Normal VG and Big VG is 1 GB and in case of scalable VG it is 128 G.
My Questions:
1) What is the min PP size allowed for Normal VG, Big VG and Scalable VG?
2) Why is the max PP Size in Normal and Big VG is 1 G and 128 G in... (1 Reply)
My volume group of size 200 gb.
out of which only 100 gb is used by 2 logical volumes /dev/vg00/lvol0 and /dev/vg00/lvol0 respectively (both are 50 gb each).
Whenever i use vgreduce command to reduce the size of volume group i get below error.
# vgreduce vg00 -a
Physical volume... (16 Replies)
Hi,
I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies
1)Physical Volume
2)Volume Group
3)Logical Volume
4)Physical Partition
Please help me to understand these concepts. (6 Replies)
hi,
I want to create a volume group of 200 GB and then create different file systems on that.
please help me out. Its becomes confusing when the PP calculating PP.
I don't understand this concept. (2 Replies)
hello, i am running an AIX6.1 machine and i am trying to restore a volume group that i backed up using mkvgdata command from another server. although i checked file .data and i make sure that PP size for this volume group is 128, when i run restvg command to restore it, it fails because it... (2 Replies)
Hello Guys,
I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var.
I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 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)