Storage: ZFS: Difference between revisions

From Proxmox VE
Jump to navigation Jump to search
No edit summary
 
(225 intermediate revisions by 16 users not shown)
Line 1: Line 1:
== How to install ZFS-fuse under Proxmox ==
<!--PVE_IMPORT_START_MARKER-->
 
<!-- Do not edit - this is autogenerated content -->
(Tested with Kernel 2.6.32)
{{#pvedocs:pve-storage-zfspool-plain.html}}
 
[[Category:Reference Documentation]]
  apt-get install build-essential libaio-dev libattr1-dev libacl1-dev libz-dev libz-dev libfuse-dev libfuse2 scons libssl-dev
<pvehide>
  wget -nd http://zfs-fuse.net/releases/0.6.0/zfs-fuse-0.6.0.tar.bz2
Storage pool type: zfspool
  tar jxvf zfs-fuse-0.6.0.tar.bz2
This backend allows you to access local ZFS pools (or ZFS file systems
  cd zfs-fuse-0.6.0
inside such pools).
  cd src
Configuration
  scons
The backend supports the common storage properties content, nodes,
  scond install
disable, and the following ZFS specific properties:
 
pool
Fire up ZFS-fuse daemon
Select the ZFS pool/filesystem. All allocations are done within that
  /usr/local/sbin/zfs-fuse
pool.
 
blocksize
Create Zpool
Set ZFS blocksize parameter.
  zpool create -m /var/lib/vz/images2 /dev/sdb
sparse
 
Use ZFS thin-provisioning. A sparse volume is a volume whose
Create ZFS
reservation is not equal to the volume size.
  zfs create images2/109
mountpoint
 
The mount point of the ZFS pool/filesystem. Changing this does not
ZFS clone a vm 109 to vm 110
affect the mountpoint property of the dataset seen by zfs.
  zfs snapshot images2/109@master
Defaults to /&lt;pool&gt;.
  zfs clone images2/109@master images2/110
Configuration Example (/etc/pve/storage.cfg)
 
zfspool: vmdata
== Debian GNU/kFreeBSD ==
        pool tank/vmdata
 
        content rootdir,images
zfs work much better using  Debian/GNU kFreeBSD
        sparse
 
File naming conventions
after installing the system to kvm or hardware:
The backend uses the following naming scheme for VM images:
 
vm-&lt;VMID&gt;-&lt;NAME&gt;      // normal VM images
*add some disks .  in KVM i was only able to get ide to work.
base-&lt;VMID&gt;-&lt;NAME&gt;    // template VM image (read-only)
 
subvol-&lt;VMID&gt;-&lt;NAME&gt; // subvolumes (ZFS filesystem for containers)
*the scsi disks look like:
&lt;VMID&gt;
<pre>
This specifies the owner VM.
ls /dev/ad*
&lt;NAME&gt;
/dev/ad10 /dev/ad10s1  /dev/ad10s2  /dev/ad11  /dev/ad12  /dev/ad13
This can be an arbitrary name (ascii) without white space. The
</pre>
backend uses disk[N] as default, where [N] is replaced by an
 
integer to make the name unique.
 
Storage Features
*clear the partition tables. just not the operating system disk!  per http://www.solarisinternals.com/wiki/index.php/ZFS_Best_Practices_Guide  - if I read it right - use entire disk not slices for zfs .  I used
ZFS is probably the most advanced storage type regarding snapshot and
<pre>
cloning. The backend uses ZFS datasets for both VM images (format
fdisk /dev/ad11
raw) and container data (format subvol). ZFS properties are
o
inherited from the parent dataset, so you can simply set defaults
w
on the parent dataset.
</pre>
Table 1. Storage features for backend zfs
then same for ad12 and ad13
Content types
 
Image formats
Shared
*install this
Snapshots
aptitude install zfsutils
Clones
 
images rootdir
*make a pool
raw subvol
 
no
*links
yes
yes
Examples
It is recommended to create an extra ZFS file system to store your VM images:
# zfs create tank/vmdata
To enable compression on that newly allocated file system:
# zfs set compression=on tank/vmdata
You can get a list of available ZFS filesystems with:
# pvesm zfsscan
See Also
Storage
ZFS on Linux
</pvehide>
<!--PVE_IMPORT_END_MARKER-->

Latest revision as of 08:08, 6 December 2019

Storage pool type: zfspool

This backend allows you to access local ZFS pools (or ZFS file systems inside such pools).

Configuration

The backend supports the common storage properties content, nodes, disable, and the following ZFS specific properties:

pool

Select the ZFS pool/filesystem. All allocations are done within that pool.

blocksize

Set ZFS blocksize parameter.

sparse

Use ZFS thin-provisioning. A sparse volume is a volume whose reservation is not equal to the volume size.

mountpoint

The mount point of the ZFS pool/filesystem. Changing this does not affect the mountpoint property of the dataset seen by zfs. Defaults to /<pool>.

Configuration Example (/etc/pve/storage.cfg)
zfspool: vmdata
        pool tank/vmdata
        content rootdir,images
        sparse

File naming conventions

The backend uses the following naming scheme for VM images:

vm-<VMID>-<NAME>      // normal VM images
base-<VMID>-<NAME>    // template VM image (read-only)
subvol-<VMID>-<NAME>  // subvolumes (ZFS filesystem for containers)
<VMID>

This specifies the owner VM.

<NAME>

This can be an arbitrary name (ascii) without white space. The backend uses disk[N] as default, where [N] is replaced by an integer to make the name unique.

Storage Features

ZFS is probably the most advanced storage type regarding snapshot and cloning. The backend uses ZFS datasets for both VM images (format raw) and container data (format subvol). ZFS properties are inherited from the parent dataset, so you can simply set defaults on the parent dataset.

Table 1. Storage features for backend zfs
Content types Image formats Shared Snapshots Clones

images rootdir

raw subvol

no

yes

yes

Examples

It is recommended to create an extra ZFS file system to store your VM images:

# zfs create tank/vmdata

To enable compression on that newly allocated file system:

# zfs set compression=on tank/vmdata

You can get a list of available ZFS filesystems with:

# pvesm zfsscan