Sponsored Content
Operating Systems Solaris How to create metadb with zpool in Solaris 11 Post 302553578 by christr on Thursday 8th of September 2011 02:34:45 AM
Old 09-08-2011
You want copies of the meta database on both disks you're mirroring, and you would want them to have the same VTOC. If ZFS is taking up the entire physical disk then there won't be anywhere to put your metadb. I don't see you having any other option other than possibly setting up metadb on non-root disks.
This User Gave Thanks to christr For This Post:
 

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
vxsplitlines(1M)														  vxsplitlines(1M)

NAME
vxsplitlines - show disks with conflicting configuration copies in a cluster SYNOPSIS
vxsplitlines [-g diskgroup] [-c daname] DESCRIPTION
If you import portions of a disk group on different systems, this can lead to conflicting configuration copies on the disks of the disk group. If the configuration information in a disk group is ambiguous, it may not be possible for Veritas Volume Manager to determine which config- uration copy is most up-to-date. (This is usually termed a serial split brain (SSB) condition when it occurs in a cluster.) You cannot import a disk group in this state unless you specify which disk's configuration copy to use. You can use the vxsplitlines command to see which disks in a disk group have conflicting configuration copies, and use this information together with your knowledge of the history of the disk groups' usage to determine which configuration copy is most valid. The output from vxsplitlines displays the vxdg commands that you can run to import the disk group using the available configuration copies. The -o selectcp option of the vxdg import command is used to select the configuration copy to use for the import. OPTIONS
-c daname Display the SSB IDs for each disk that are stored in the configuration copy on the disk specified by its disk access name. Note: Although the SSB IDs for some disks may match, this does not necessarily mean that those disks' configuration copies have recorded all the configuration changes. When viewed from some other configuration copies, the SSB IDs of the same disks may not match. -g diskgroup Specifies the disk group. If a disk group is not specified, the default disk group is used as determined from the rules on the vxdg(1M) manual page. EXAMPLES
Display the disks on each side of the split in the disk group newdg: vxsplitlines -g newdg Display the SSB IDs stored in the configuration copy on disk c2t4d0: vxsplitlines -g newdg -c c2t4d0 NOTES
The vxsplitlines is primarily intended to be used with private disk groups, but it also works with shared disk groups. The version number of the disk group must be 110 or greater. SEE ALSO
vxdg(1M) Veritas Volume Manager Administrator's Guide VxVM 5.0.31.1 24 Mar 2008 vxsplitlines(1M)
All times are GMT -4. The time now is 10:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy