How to split a zfs/zpool mirror for backout purposes? Post: 302954030

9 More Discussions You Might Find Interesting

1. Solaris

zfs mirror disk

Is it possible to create a Mirror with zfs ?? I'm experimented user with Solstice Disk suite. Or Sun Volume manager or veritas volume manager. But, i would like switch from Disksuite to Zfs. All my mirrored disks.

2. Solaris

ZFS Mirror versus Hardware Mirror

I've looked a little but haven't found a solid answer, assuming there is one. What's better, hardware mirroring or ZFS mirroring? Common practice for us was to use the raid controllers on the Sun x86 servers. Now we've been using ZFS mirroring since U6. Any performance difference? Any other...

3. Solaris

Zfs::zpool.cache file

Hi All, I am trying to read zpool.cache file to find out pool information like pool name, devices it uses and all properties. File seems to be in packed format.I am not sure how to unpack it. But from opensolaris code base we can see that they have used libz for uncompromising this file, but...

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

5. Solaris

[Q] zpool mirror; read from preferred vdev(s)

Hallo, Using a zpool mirror; is there a way to set something like a primary storage / preferred vdevs / read-first devices like it was in disksuite using "metaparam -r " or the "vxvol rdpol " to define a preferred plex in VxVM? Will ZFS always use round-robin? In our example we want to use a...

6. Solaris

Zpool /ZFS recovery

running VM server for Sparc on a Solaris 11 server. I have a Guest LDOm that had two seperate zpools running, one for the zones and one for the OS. The OS was corrupted and had to be replaced. The zones zfs file system is intact I think. I still have access to the disk and can still see it in...

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

8. Solaris

Is there any GUI or web ui to administrate zfs/zpool

HI, Is there any GUI or web ui to administrate zfs/zpool. i want to monitor/expand/migrate zfs from one machine to another machine

9. Solaris

Restore of Netapp FC lun targets used as the disks for a zpool with exported zfs file systems

So, We have a Netapp storage solution. We have Sparc T4-4s running with LDOMS and client zones in the LDOMS, We are using FC for storage comms. So here's the basic setup FC luns are exported to the primary on the Sparc box. using LDM they are then exported to the LDOM using vdisk. at the...

LEARN ABOUT HPUX

vxvmboot

vxvmboot(1M)															      vxvmboot(1M)

NAME

       vxvmboot - prepare Veritas Volume Manager volume as a root, boot, primary swap or dump volume

SYNOPSIS

       /sbin/vxvmboot [-b|-d|-r|-s] [-v] -o offset -l length rawpath

       /sbin/vxvmboot -v rawpath

       /sbin/vxvmboot -c

DESCRIPTION

       The  vxvmboot  command updates information in the LABEL file for the lif disk specified by the pathname of its character (raw) device node,
       rawpath.  The volume at the specified offset and length becomes the boot, root, primary swap or dump volume when the system is next booted.

       This command is normally invoked by the vxbootsetup utility.

OPTIONS

       -b	 Specifies the volume type as a boot volume with name standvol.

       -c	 Is used to update the /stand/rootconf file with the offset and length of the rootvol. The usage is slightly different when the -c
		 argument  is  used.  The rawpath argument is not used with this invocation. Instead the path of the boot device is extracted from
		 the /stand/bootconf file.  Also, the -o and -l arguments are not used to specify the offset and length.  Instead, the offset  and
		 length of the rootvol are obtained from the LIF LABEL file on the boot device.

		 The  -c  option would normally be used in the sbin/ioinitrc script to update the /stand/rootconf file, when the boot disk is VxVM
		 rootable.

       -d	 Specifies the volume type as a dump volume with name dumpvol.

		 If a dumpvol volume exists on the specified disk, the extent information from this volume is used. If no such volume exists,  the
		 extent information of the swap volume is used instead, and swapvol performs the dual role of swap device and dump device.

       -l length Specifies the length of the volume in units of 1024-byte blocks.

       -o offset Specifies the start of the volume as the number of 1024-byte blocks from the beginning of the disk.

       -r	 Specifies the volume type as a root volume with name rootvol.

       -s	 Specifies the volume type as a swap volume with name swapvol.

       -v	 When  used with one of the options -b, -d, -r or -s, displays the contents of the updated LABEL file.	Otherwise, this option may
		 be used to display the contents of the LABEL file on the specified lif disk.

	      Note: The -b, -c, -d, -r and -s options are mutually exclusive.  If more than one of these options is specified, the  vxvmboot  com-
	      mand exits without performing any operation.

ARGUMENTS

       rawpath	 Specifies the pathname of the character (raw) device node for the lif disk.

SEE ALSO

       lif(4), mkboot(1M), vxbootsetup(1M)

VxVM 5.0.31.1							    24 Mar 2008 						      vxvmboot(1M)