Sponsored Content
Operating Systems Solaris How to create metadb with zpool in Solaris 11 Post 302553586 by DukeNuke2 on Thursday 8th of September 2011 03:02:38 AM
Old 09-08-2011
also your system seems to be a cluster and if you need to share the disks between the hosts, a metaset or a zpool is the only way (beside a vxvm volume) to achieve this...
 

10 More Discussions You Might Find Interesting

1. 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

2. 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

3. Solaris

zpool create - long time creation

Hello, I have a 520GB SAN resource connected to the server via FC (4Gbit). In the next step he wants to create pool storage: After 15 hours Pool has not yet created... Is such a long waiting time is normal? Should I have done? Regards (1 Reply)
Discussion started by: bieszczaders
1 Replies

4. Solaris

Increase root filesystem on solaris zone using zpool

I have a solaris zone of 12 GB and i have to increase the / filesystem to 31GB as requested. Earlier I had expanded filesystems other than / by setting quota to new value like "zfs set quota=new value mountpoint" but I am not sure whether its a good practice in zfs because by default in my... (5 Replies)
Discussion started by: vikkash
5 Replies

5. BSD

Unable to create zfs zpool in FreeBSD 8.2: no such pool or dataset

I am trying to test simple zfs functionality on a FreeBSD 8.2 VM. When I try to run a 'zpool create' I receive the following error: # zpool create zfspool /dev/da0s1a cannot create 'zfspool': no such pool or dataset # zpool create zfspool /dev/da0 cannot create 'zfspool': no such pool or... (3 Replies)
Discussion started by: bstring
3 Replies

6. Solaris

Check Solaris VM Databases metadb does not have enough information about logical volumes

Check Solaris VM Databases metadb does not have enough information about logical volumes. Current value is 0% I have checked the SVM status, all disks are good state and synched perfectly. no errors in metadb -i. what is this alert exact mean? what we have to check for the value? Please... (1 Reply)
Discussion started by: Naveen.6025
1 Replies

7. Solaris

Upgrading Solaris - what happens to zpool/zfs versions

Hi everyone, I'm hoping someone can help me out here. I've googled lots and don't think I can find an easy answer to this. We're in the process of upgrading Solaris from v10 5/08 to v10 9/10. The zpools for luns are currently at version 10, and I understand Solaris v10 9/10 has support for... (3 Replies)
Discussion started by: badoshi
3 Replies

8. UNIX for Advanced & Expert Users

Solaris 10: I forgot to detach a zone before zpool export. Uninstall zone?

Dear all, recently, I migrated a solaris zone from one host to another. The zone was inside of a zpool. The zpool cotains two volumes. I did the following: host1: $ zlogin zone1 shutdown -y -g0 -i0 #Zone status changes from running to installed $ zpool export zone1 host2: $ zpool... (2 Replies)
Discussion started by: custos
2 Replies

9. Solaris

Solaris 10 Volume Manager - adding slice to metadb

Hi all, I added a new disk slice to the current metadb. Below is what I see bash-3.2# metadb -i flags first blk block count a m p luo 16 8192 /dev/dsk/c0t0d0s7 a p luo 8208 8192 ... (3 Replies)
Discussion started by: javanoob
3 Replies

10. Solaris

Solaris can not boot because metadb lost

how to recovery metadb? Thanks! (1 Reply)
Discussion started by: dzung
1 Replies
scconf_dg_vxvm(1M)					  System Administration Commands					scconf_dg_vxvm(1M)

NAME
scconf_dg_vxvm - add, change, or update VxVM device group configuration. SYNOPSIS
scconf -a -D type=vxvm,devicegroup-options[,localonly=true|false] scconf -c -D devicegroup-options[,sync] scconf -r -D name=devicegroupname DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. The following information is specific to the scconf command. To use the equivalent object-oriented commands, see the cldevicegroup(1CL) man page. The scconf_dg_vxvm command is used to add, change, and remove the VERITAS Volume Manager (VxVM) device groups to the Sun Cluster device- groups configuration. OPTIONS
See the scconf(1M) man page for the list of supported generic device-group options. The following action options describe the actions that the command performs. Only one action option is allowed in the command. -a Add a VxVM device group to the cluster configuration. The -a (add) option adds a new VxVM device group to the Sun Cluster device-groups configuration. With this option you define a name for the new device group, specify the nodes on which this group can be accessed, and specify a set of properties used to control actions. For VxVM device groups, you can only assign one VxVM disk group to a device group, and the device-group name must always match the name of the VxVM disk group. You cannot create a VxVM device group unless you first import the corresponding VxVM disk group on one of the nodes in that device's node list. Before you can add a node to a VxVM device group, every physical disk in the disk group must be physically ported to that node. After you register the disk group as a VxVM device group, you must first deport the disk group from the current node owner and turn off the auto-import flag for the disk group. To create a VxVM device group for a disk group, you must run the scconf command from the same node where the disk group was created. -c Change the ordering of the node preference list, change preference and failback policy, and change the desired number of sec- ondaries. The scconf -c (change) option changes the order of the potential primary node preference, to enable or disable failback, to add more global devices to the device group, and to change the desired number of secondaries. The sync suboption is used to synchronize the clustering software with VxVM disk-group volume information. The sync suboption is only valid with the change form of the command. Use the sync suboption whenever you add or remove a VxVM volume from a VxVM device group or change any volume attribute, such as owner, group, or access permissions. Also use the sync suboption to change a device-group configuration to a replicated or non-replicated configuration. For device groups that contain disks that use Hitachi TrueCopy data replication, this sync suboption synchronizes the device- group configuration and the replication configuration. This synchronization makes Sun Cluster software aware of disks that are configured for data replication and enables the software to handle failover or switchover as necessary. After you create a Solaris Volume Manager disk set that contain disks that are configured for replication, you must run the sync suboption for the corresponding svm or sds device group. A Solaris Volume Manager disk set is automatically registered with Sun Cluster software as an svm or sds device group, but replication information is not synchronized at that time. For newly created vxvm and rawdisk device-group types, you do not need to manually synchronize replication information for the disks. When you register a VxVM disk group or a raw-disk device group with Sun Cluster software, the software automatically discovers any replication information on the disks. To change the order-of-node preference list from false to true, you must specify in the nodelist all the nodes that currently exist in the device group. You must also set the preferenced suboption to true. If you do not specify the preferenced suboption with the change form of the command, the already established true or false setting is used. If a disk group should be accessed by only one node, it should be configured with the localonly property set to true. This property setting puts the disk group outside the control of Sun Cluster software. Only one node can be specified in the node list to create a localonly disk group. To change a local-only disk group to a regular VxVM disk group, set the localonly property to false. -r Remove the specified VxVM device group from the cluster. The -r (remove) option removes a VxVM device group from the Sun Cluster device-groups configuration. You can also use this form of command to remove the nodes from the VxVM device group configuration. EXAMPLES
Example 1 Using scconf Commands The following scconf commands create a VxVM device group, change the order of the potential primary nodes, change the preference and fail- back policy for the device group, change the desired number of secondaries, and remove the VxVM device group from the cluster configura- tion. host1# scconf -a -D type=vxvm,name=diskgrp1,nodelist=host1:host2:host3,preferenced=false,failback=enabled host1# scconf -c -D name=diskgrp1,nodelist=host2:host1:host3,preferenced=true,failback=disabled,numsecondaries=2 sync host1# scconf -r -D name=diskgrp1,nodelist=node1 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWscu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), cldevicegroup(1CL), scconf(1M), attributes(5) Sun Cluster 3.2 2 Aug 2006 scconf_dg_vxvm(1M)
All times are GMT -4. The time now is 02:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy