So, first I created a ZFS pool out of two slices on two disks. This is not really recommended way to create ZFS pool. You should really be using two whole disks. And, ignore the fact that those disks both reside on the same controller. Right after that I created dev1 filesystem within the zonepool:
bash-3.00# zpool create -m /export/home/zones zonepool mirror c0t0d0s3 c0t1d0s3
bash-3.00# zfs create zonepool/dev1
bash-3.00# zfs list
NAME USED AVAIL REFER MOUNTPOINT
zonepool 122K 55.6G 25.5K /export/home/zones
zonepool/dev1 24.5K 8.00G 24.5K /export/home/zones/dev1
Next I set ZFS quota on the filesystem to 8GB:
bash-3.00# zfs set quota=8G zonepool/dev1
bash-3.00# zfs get all zonepool/dev1
NAME PROPERTY VALUE SOURCE
zonepool/dev1 type filesystem -
zonepool/dev1 creation Fri Jun 4 9:17 2010 -
zonepool/dev1 used 24.5K -
zonepool/dev1 available 8.00G -
zonepool/dev1 referenced 24.5K -
zonepool/dev1 compressratio 1.00x -
zonepool/dev1 mounted yes -
zonepool/dev1 quota 8G local
zonepool/dev1 reservation none default
zonepool/dev1 recordsize 128K default
zonepool/dev1 mountpoint /export/home/zones/dev1 inherited from zonepool
zonepool/dev1 sharenfs off default
zonepool/dev1 checksum on default
zonepool/dev1 compression off default
zonepool/dev1 atime on default
zonepool/dev1 devices on default
zonepool/dev1 exec on default
zonepool/dev1 setuid on default
zonepool/dev1 readonly off default
zonepool/dev1 zoned off default
zonepool/dev1 snapdir hidden default
zonepool/dev1 aclmode groupmask default
zonepool/dev1 aclinherit secure default
zonepool/dev1 canmount on default
zonepool/dev1 shareiscsi off default
zonepool/dev1 xattr on default
Now, I should mention, that prior to configuring /export/home/zones to reside on ZFS I uninstalled dev1 container which was there previously. So, the container itself was gone, but the system still had knowledge of the container’s configuration. I wrote a post on configuring containers here.
bash-3.00# zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
- dev1 configured /export/home/zones/dev1 native shared
Since the container was already configured, I went ahead and started installing it:
bash-3.00# zoneadm -z dev1 install
/export/home/zones/dev1 must not be group readable.
/export/home/zones/dev1 must not be group executable.
/export/home/zones/dev1 must not be world readable.
/export/home/zones/dev1 must not be world executable.
could not verify zonepath /export/home/zones/dev1 because of the above errors.
zoneadm: zone dev1 failed to verify
bash-3.00#
Woops, looks like the container directory permissions need some fixing:
bash-3.00# cd /export/home/zones/
bash-3.00# ls -l
total 3
drwxr-xr-x 2 root sys 2 Jun 3 09:48 dev1
bash-3.00# chmod 700 dev1
bash-3.00# chown root:root dev1
One more try to install the container:
bash-3.00# zoneadm -z dev1 install
Preparing to install zone .
Creating list of files to copy from the global zone.
Copying <2561> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1086> packages on the zone.
Initialized <1086> packages on zone.
Zone is initialized.
The file contains a log of the zone installation.
That’s it. After the container install completed, before booting dev1, I stuck the following sysidcfg file into /etc directory of dev1 container:
bash-3.00# more sysidcfg
system_locale=en_US
timezone=US/Central
terminal=vt100
security_policy=NONE
network_interface=primary {
hostname=dev1
}
nfs4_domain=dynamic
name_service=NIS {
domain_name=example.com
name_server=nis1(10.1.1.1)
}
That way I would not be asked any container configuration questions during first container boot. Except for the root password, of course.
]]>Here is how it looks in format command:
partition> p
Current partition table (original):
Total disk sectors available: 73383902 + 16384 (reserved sectors)
Part Tag Flag First Sector Size Last Sector
0 usr wm 34 34.99GB 73383902
1 unassigned wm 0 0 0
2 unassigned wm 0 0 0
3 unassigned wm 0 0 0
4 unassigned wm 0 0 0
5 unassigned wm 0 0 0
6 unassigned wm 0 0 0
8 reserved wm 73383903 8.00MB 73400286
If you use straight format command there is no way to get rid of EFI label. Instead, you have to use -e option with format to get to expert features:
bash-3.00# format -e
With -e options when you label the LUN you will be asked about the type of label you want to put on the disk:
format> label
[0] SMI Label
[1] EFI Label
Specify Label type[1]: 0
Warning: This disk has an EFI label. Changing to SMI label will erase all
current partitions.
Continue? y
Auto configuration via format.dat[no]? yes
I suppose you could alternatively use dd command and blank out the whole disk.
]]>zpool create [pool_name] [device] [device] ...
zpool create datapool c5t433127A900011C370000C00003210000d0 c5t433127B4001031250000900000540000d0
Create mirrored pool:
zpool create [pool_name] mirror [device] [device] ...
zpool create datapool mirror c5t433127A900011C370000C00003210000d0 c5t433127B4001031250000900000540000d0
Create Raid-Z pool:
zpool create [pool_name] raidz [device] [device] [device] ...
zpool create datapool raidz c5t433127A900011C370000C00003210000d0 c5t433127B4001031250000900000540000d0 c5t439257C4000019250000900000540000d0
Transform simple pool to a mirror:
zpool create [pool_name] [device]
zpool attach [pool_name] [existing_device] [new_device]
zpool create datapool c5t433127A900011C370000C00003210000d0
zpool attach datapool c5t433127A900011C370000C00003210000d0 c5t433127B4001031250000900000540000d0
Expand simple pool:
zpool create [pool_name] [device]
zpool add [pool_name] [new_device]
zpool create datapool c5t433127A900011C370000C00003210000d0
zpool add datapool c5t433127B4001031250000900000540000d0
Expand mirrored pool by attaching additional mirror:
zpool add [pool_name] mirror [new_device] [new_device]
zpool add datapool mirror c5t433127A900011C370000C00003460000d0 c5t433127B400011C370000C00003410000d0
Replace device in a pool:
zpool replace [pool_name] [old_device] [new_device]
zpool replace datapool c5t433127A900011C370000C00003410000d0 c5t433127B4001031250000900000540000d0
Destroy pool:
zpool destroy [pool_name]
zpool destroy datapool
Set pool mountpoint:
zfs set mountpoint=/path [pool_name]
zfs set mountpoint=/export/zfs datapool
Display configured pools:
zpool list
zpool list
Display pool status info:
zpool status [-v] [pool_name]
zpool status -v datapool
Display pool I/O statistics:
zpool iostat [pool_name]
zpool iostat datapool
Display pool command history:
zpool history [pool_name]
zpool history datapool
Export a pool:
zpool export [pool_name]
zpool export datapool
Import a pool:
zpool import [pool_name]
zpool import datapool
Create a filesystem:
zfs create [pool_name]/[fs_name]
zfs create datapool/filesystem
Destroy a filesystem:
zfs destroy [pool_name]/[fs_name]
zfs destroy datapool/filesystem
Rename a filesystem:
zfs rename [pool_name]/[fs_name] [pool_name]/[fs_name]
zfs rename datapool/filesystem datapool/newfilesystem
Move a filesystem:
zfs rename [pool_name]/[fs_name] [pool_name]/[fs_name]/[fs_name]
zfs rename datapool/filesystem datapool/users/filesystem
Display properties of a filesystem:
zfs get all [pool_name]/[fs_name]
zfs get all datapool/filesystem
Make a snapshot:
zfs snapshot [pool_name]/[fs_name]@[time]
zfs snapshot datapool/filesystem@friday
Roll back filesystem to its snapshot:
zfs rollback [pool_name]/[fs_name]@[time]
zfs rollback datapool/filesystem@friday
Clone a filesystem:
zfs snapshot [pool_name]/[fs_name]@[time]
zfs clone [pool_name]/[fs_name]@[time] [pool_name]/[fs_name]
zfs snapshot datapool/filesystem@today
zfs clone datapool/filesystem@today datapool/filesystemclone
Backup filesystem to a file:
zfs send [pool_name]/[fs_name] > /path/to/file
zfs send datapool/filesystem@friday > /tmp/filesystem.bkp
Restore filesystem from a file:
zfs receive [pool_name]/[fs_name] < /path/to/file
zfs receive datapool/restoredfilesystem < /tmp/filesystem.bkp
Create ZFS volume:
zfs create -V [size] [pool_name]/[vol_name]
zfs create -V 100mb datapool/zvolume
newfs /dev/zvol/dsk/datapool/zvolume