Using zvols as swap devices does create deadlocks for users, as of zfs 0.7.9.
As the discussion of the issue [0] shows, fixing this is involved, and probably
won't be happening anytime soon (before zfs 0.8).
Not creating swap as a zvol seems like the better default setting for now.
Users needing swap can either leave unpartitioned space, by setting minfree,
or create the zvol quite easily after installation
[0] https://github.com/zfsonlinux/zfs/issues/7734
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
Pass $config_options->{hdsize} to partition_bootable_disk, where needed,
and do the unitconversion in partition_bootable_disk.
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
Change partition_bootable_disk:
* Increase the efi-esp partitions' size to 512M (from 256M)
* Create the bios_boot partition in the first MB (sectors 34:2047)
* Split the sgdisk invocation into 2, to get 1M alignment for efi and os
partitions
Changes are inspired by the wiki-entries by zol-upstream [0].
Use partition_bootable_disk also for bootable ZFS disks.
This provides users with the opportunity to leave unpartitioned space at
the end of the disk (by setting the hdsize parameter) for use outside of ZFS
(e.g. to create a dedicated swap partition).
[0] https://github.com/zfsonlinux/zfs/wiki/Debian-Stretch-Root-on-ZFS
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
The iso 3166-1 information in the iso-codes package seems to be more
up to par than the one that was used from tzdata. Also remove
obsolete comments.
Signed-off-by: Rhonda D'Vine <rhonda@proxmox.com>
Some customers have more than 26 devices,
for example, if they use multipath on a DAS box.
In the Linux Documentation admin-guide/devices.txt
is written 256 SCSI disk devices are possible.
Signed-off-by: Wolfgang Link <w.link@proxmox.com>
inkscape pulls in a lot of dependencies and we explicitly made the
switch to the more lightweight rsvg-convert, provided through the
librsvg2-bin package in pve-docs, so do here the same.
if no thin pool has been created (requested or because of lack of
space), don't reference it in storage.cfg
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
and take metadata out of the (potential) data space, not the
reserved/minfree space.
also avoid creating very small thin pools.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
