I need some advice please. I have this server with a couple of zpools, lets call them
pay_serv
ukb_pool
There are two zones attached to these pools. When I do a zfs list I see this
Now the pay_serv zone is mounted on /pay_serv/ps and the ukb zone on /ukb_pool/ukb. I see these are technically stored in the ukb_pool disks so what I want to do is destroy the pay_serv zpool and free that up for something else.
If I stop the pay_serv zone and then do a "zfs umount /pay_serv" and then a "zfs destroy pay_serv" will that mess up the /pay_serv/ps directory. I am presuming yes and I am scared in doing this as it contains live data and is most definitely not a test server.
Please help!
Thanks....
Last edited by DukeNuke2; 10-20-2011 at 01:16 PM..
Hi community,
I've a hard question for you.
1)What are the differences between ZFS and Veritas Volume Manager on Solaris10?
2) what is the difference to manage the internal disks (Mirror)?
3) what is the difference to manage the external disks?
4) What is the difference to manage... (5 Replies)
I have a oracle instance running in NGZ which is on zfs dataset. Is there any possibility if i can take a zfs snapshot without shutting down the zone and then restore the zfs on other server and start oracle .. will the data be fine or not ? (2 Replies)
With Solaris 11 coming out with a requirement of ZFS on the root disk, I was curious to know who is using the Zeta File System now?
I have been using ZFS for the past year and don't plan to go back to UFS since ZFS is much more reliable and easier to maintain. (13 Replies)
Hi, I am nowusing ZFS since some weeks and now I have 2 questions:
1) in zpool I saw some disk added with the *s2 at the end, I have in mind that should not be ? is this right and if so can I get the *s2 disk out of the zpool ?
2) Zpool has still 2 spare disk but when I try to create a new... (6 Replies)
I have installed Solaris 11 Express on my server and want to set up automatic backuping using zfs snapshots. In the backup script I need to find out the name of the last snapshot of the given filesystem (in order to refer to it as the startpoint of an incremental backup). What is the best way to do... (4 Replies)
I am building a new server on sol10_X86.
I am new to ZFS, this will be one of the first systems to use it.
I would like to have /opt /usr and a /u01 as separate file systems from the main ZFS pool. I know that this goes against the basic idea of ZFS, but this is so I can restrict the size/usage... (1 Reply)
Hi all,
A customer has a very active ZFS partitionon their production system, I need to get a copy of the data under one directory at a specific point in time.
Is it possible to do this with the ZFS snapshot/clone tools, (and what commands should be used to capture the info I require for... (6 Replies)
Hi guys! I am student from poland and I am preparing my assignment about Solaris 11 cloud computing capabilities. :p
I am writing about ZFS now, and as I am quite new to this stuff I have several question (I prefere to have deep understanding of what I am doing, instead of just rewriting the... (1 Reply)
Discussion started by: mlody94
1 Replies
LEARN ABOUT FREEBSD
gptzfsboot
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