10 More Discussions You Might Find Interesting
1. Solaris
Hi
Please let me know how to increase the size of rpool in solaris 11 in ldom. I know how to map the new LUN to LDOM after that please let me know the procedure to increase the rpool and how to identify new disk in OBP level of ldom as I need to set the new/lun to be my new boot device. (5 Replies)
Discussion started by: hb00
5 Replies
2. Solaris
I have a 240GB disk as rpool. I have installed Solaris 11.3 to a partition which is 110GB. Now I have another 130GB which is unallocated. I want to use that additional space as a temporary folder to be shared between Solaris and Linux. The additional space had no /dev/dsk/c2t4... entry so I used... (8 Replies)
Discussion started by: kebabbert
8 Replies
3. Solaris
Hello,
I need some help mirroring my rpool.
I have a 60gb ssd running the rpool alone and want to mirror it for redundancy so I bought a 120gb ssd that I found for a good price. 60gb drives aren't as easy to find at a good price anymore it seems.
I (a bit naively) thought after reading... (9 Replies)
Discussion started by: Zorken
9 Replies
4. Solaris
Hi,
I am unable to understand that, in one of my servers while
df -kh
Filesystem Size Used Available Capacity Mounted on
rpool/ROOT/solaris-2 98G 11G 29G 29% /
Even the Root FS filled on 40gb and system becomes unstable.
it is showing... (4 Replies)
Discussion started by: anuragr
4 Replies
5. Solaris
Hi everyone,
I am doing housekeeping of my Solaris 11 for zfs snapshot to reduce the snapshot size. I have already cleared the / file system, however the rpool size still not reduced.
Filesystem Size Used Available Capacity Mounted on
rpool/ROOT/solaris-2 98G 6.9G ... (2 Replies)
Discussion started by: freshmeat
2 Replies
6. Solaris
Hi,
I have rpool about 500G. So i want to use 210G from rpool and assign mount point as /database.
I seek in google and couldn't found it. Does anyone know how to achieve it?
Thanks. (2 Replies)
Discussion started by: mzainal
2 Replies
7. Solaris
Hi guys,
I have a Solaris 10 x86 server with 2 physical disks. It had a ZFS rpool on the first disk c0t0d0s0. The server stopped booting with some error like "Cannot find bootfile".
I booted with Solaris DVD and re-installed the operating system on the second disk with a different pool... (0 Replies)
Discussion started by: ARPcPro
0 Replies
8. Solaris
Hi All;
My server's root partition was encapsulated with VxVM, I try to convert it to ZFS. I successfully de-encapsulated root. Now I try to mirror 2 root disks using ZFS. But I receive following error:
# zpool create rpool mirror c0t0d0s0 c0t1d0s0
invalid vdev specification
use '-f' to... (6 Replies)
Discussion started by: reseki
6 Replies
9. Solaris
I'd like to finish setting up this system and then move the secondary or primary disk to another system that is the exact same hardware.
I've done things like this in the past with ufs and disk suite mirroring just fine. But I have yet to do it with a zfs root pool mirror.
Are there any... (1 Reply)
Discussion started by: Metasin
1 Replies
10. Solaris
Hi,
We have a Sun M5000. I am now trying to boot the second system domain by using the boot disk (a mirrored boot disk actually) of the first domain (if succeed then no OS installation is needed for the second domain). I got the following errors:
SPARC Enterprise M5000 Server, using Domain... (21 Replies)
Discussion started by: aixlover
21 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