Sponsored Content
Operating Systems Solaris after ZFS can not restore VTOC of disk.. Post 302239291 by incredible on Tuesday 23rd of September 2008 08:42:32 AM
Old 09-23-2008
You can use a disk or slice as either part of an SVM volume or as part of a ZFS storage pool. Do not use the same disk or slice in both an SVM and ZFS configuration.
Did you?Smilie
 

8 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Restore to disk from tape

I have been restoring from tape some old data. I have done quite a few tapes and have had no problems until now. The command I am running is "dd if=/dev/rmt/1hbn bs=1024 | tar -pBxF - ". This is the second tape have have come up with the error "Not enough space". This tape has a couple of... (1 Reply)
Discussion started by: mtoombs
1 Replies

2. Solaris

ZFS Restore Attempt

We currently have T2000 servers attached to Sun 3320 Storage Arrays. We run a database on the 3320 devices with the storage created through ZFS. We use 3 RAIDZ2 pools and then create our partitions from those. Now onto the question. If our T2000 fails and we swap out machines is there a way... (1 Reply)
Discussion started by: buckhtr77
1 Replies

3. Solaris

Local Full Backup and Restore ZFS

Hi men, I'm testing for my backup&restore job with ZFS. My server have two disks. I wanna do backup&restore job like ufsdump utility: Disk0 is rpool(root zpool) and disk1 (backup zpool) will be stored full backup replicates. When rpool zpool have problem, i can "boot cdrom -s" and use my... (5 Replies)
Discussion started by: tien86
5 Replies

4. Solaris

Emergency - restore a deleted zfs snapshot

Hi, I deleted a zfs snapshot because it was as big as the original zfs. After the snapshot was removed, all the data in the original zfs is gone. How this happened? Can I restore the snapshot? Please help. Thanks a lot! (5 Replies)
Discussion started by: aixlover
5 Replies

5. AIX

Dd of disk contains vg and restore on another m/c

Hello gurus, I have a requirement of backup of a vg containing a file system. vg1 contains 3 LV each of 50G size. They are coming out from ~350G harddisk. and only 150G is being used. Now, i want to dd this hdisk and restore to another machine. I am not sure how to go about this. Can some... (3 Replies)
Discussion started by: abhishekdave
3 Replies

6. Solaris

ZFS Slice disk

Hi, How to to make a slice and define as ufs from zpool? Please advice me. Thanks. ---------- Post updated at 01:53 AM ---------- Previous update was at 12:24 AM ---------- Before slice: Part Tag Flag Cylinders Size Blocks 0 root wm 0 ... (2 Replies)
Discussion started by: mzainal
2 Replies

7. 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... (4 Replies)
Discussion started by: os2mac
4 Replies

8. HP-UX

How to restore from disk?

Our new rx2800 server is running HP-UX 11iV3. We have a cron script to perform an fbackup to a file on disk nightly. Now I'm trying to do a test restore, but I can't seem to find the correct way to specify the backup file as the source in frecover. Can anyone point me in the right direction? ... (5 Replies)
Discussion started by: jduehmig
5 Replies
GPTZFSBOOT(8)						    BSD System Manager's Manual 					     GPTZFSBOOT(8)

NAME
gptzfsboot -- GPT bootcode for ZFS on BIOS-based computers DESCRIPTION
gptzfsboot is used on BIOS-based computers to boot from a filesystem in a ZFS pool. gptzfsboot is installed in a freebsd-boot partition of a GPT-partitioned disk with gpart(8). IMPLEMENTATION NOTES
The GPT standard allows a variable number of partitions, but gptzfsboot only boots from tables with 128 partitions or less. BOOTING
gptzfsboot tries to find all ZFS pools that are composed of BIOS-visible hard disks or partitions on them. gptzfsboot looks for ZFS device labels on all visible disks and in discovered supported partitions for all supported partition scheme types. The search starts with the disk from which gptzfsboot itself was loaded. Other disks are probed in BIOS defined order. After a disk is probed and gptzfsboot determines that the whole disk is not a ZFS pool member, the individual partitions are probed in their partition table order. Currently GPT and MBR partition schemes are supported. With the GPT scheme, only partitions of type freebsd-zfs are probed. The first pool seen during probing is used as a default boot pool. The filesystem specified by the bootfs property of the pool is used as a default boot filesystem. If the bootfs property is not set, then the root filesystem of the pool is used as the default. zfsloader(8) is loaded from the boot filesystem. If /boot.config or /boot/config is present in the boot filesystem, boot options are read from it in the same way as boot(8). The ZFS GUIDs of the first successfully probed device and the first detected pool are made available to zfsloader(8) in the vfs.zfs.boot.primary_vdev and vfs.zfs.boot.primary_pool variables. USAGE
Normally gptzfsboot will boot in fully automatic mode. However, like boot(8), it is possible to interrupt the automatic boot process and interact with gptzfsboot through a prompt. gptzfsboot accepts all the options that boot(8) supports. The filesystem specification and the path to zfsloader(8) are different from boot(8). The format is [zfs:pool/filesystem:][/path/to/loader] Both the filesystem and the path can be specified. If only a path is specified, then the default filesystem is used. If only a pool and filesystem are specified, then /boot/zfsloader is used as a path. Additionally, the status command can be used to query information about discovered pools. The output format is similar to that of zpool status (see zpool(8)). The configured or automatically determined ZFS boot filesystem is stored in the zfsloader(8) loaddev variable, and also set as the initial value of the currdev variable. FILES
/boot/gptzfsboot boot code binary /boot.config parameters for the boot block (optional) /boot/config alternative parameters for the boot block (optional) EXAMPLES
gptzfsboot is typically installed in combination with a ``protective MBR'' (see gpart(8)). To install gptzfsboot on the ada0 drive: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 gptzfsboot can also be installed without the PMBR: gpart bootcode -p /boot/gptzfsboot -i 1 ada0 SEE ALSO
boot.config(5), boot(8), gpart(8), loader(8), zfsloader(8), zpool(8) HISTORY
gptzfsboot appeared in FreeBSD 7.3. AUTHORS
This manual page was written by Andriy Gapon <avg@FreeBSD.org>. BUGS
gptzfsboot looks for ZFS meta-data only in MBR partitions (known on FreeBSD as slices). It does not look into BSD disklabel(8) partitions that are traditionally called partitions. If a disklabel partition happens to be placed so that ZFS meta-data can be found at the fixed off- sets relative to a slice, then gptzfsboot will recognize the partition as a part of a ZFS pool, but this is not guaranteed to happen. BSD
September 15, 2014 BSD
All times are GMT -4. The time now is 07:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy