Search results

1. Manually upload VM disks to new machine. 2. Upload config files to new machines. 3. Edit config is something is needed. 4. Boot VM

For ZFS don't forget SYNC writes are written to ZFS LOG device. If you don't have external ZFS LOG device then the pool become as LOG device too. Thats mean double writes. If SYNC is important and you want good write performance then add single good SATA/NVME SSD as ZFS pool LOG device.

If its in the same pool - then no advantages.

As I know ZFS is missing I/O priority. Its works like FIFO. Like Win98 system :-)

To run KVM you need direct access to CPU. Others VM like LXC or Openvz .... do not need direct CPU access.

You can export pool and import pool with new name.

# qm showcmd 101

EFI problem? Have no xp with it.

# zpool list -> it is RAW data sizes and its have nothing to do with available space If you want more free space in rpool/ROOT/pve-1 then 1. Turn off swap. 2. Remove rpool/swap 3. Create rpool/swap with less space like 5G 4. Format swap and mount Result -> free space for zfs pool rpool

It is not a bug. Creating pool "MY_POOL" the mount point will be set to /MY_POLL. You can set mountpoint on creating pool with -m ZFS will mount fs only on empty catalog. Proxmox install script is missing: # zfs set mountpoint=none rpool/ROOT # zfs set mountpoint=none rpool

No it is default action.

This automatically did it.

bit rot | bit roll | silence corruption - the data corruption then HDD give bad data or the cable leads to distort information.

How about bit rot ?

# zfs set mountpoint=none rpool

If you know and love ZFS why you go to HW Raid? it must be you don't need data protection.

ZFS dont have protection option from deleting zvol. But you may protect in other way. Part 1 Snaps How the Proxmox and Console do snapshots on ZFS? Console -> zfs snap zvol@name Proxmox -> zfs snap zvol@name -> put info in VM config file. Looking snapshosts from console you can see all...

If your RAID is made from ZFS then you don't need to worry about HDD names.