Search results

  1. N

    Virtual box,No support for KVM virtualisation detected

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

    Cluster setup and ZFS pools

    You can export pool and import pool with new name.
  3. N

    Boot problem zfs

    EFI problem? Have no xp with it.
  4. N

    Resize root zfs on node

    # 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
  5. N

    Upgrade PVE 5.1-41 to 5.2-1 Failed to start Mount ZFS

    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
  6. N

    ZFS vs PERC H710P Mini

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

    ZFS vs PERC H710P Mini

    How about bit rot ?
  8. N

    ZFS vs PERC H710P Mini

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

    Additional ZFS Volume and VM Snapshots

    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...
  10. N

    Existing Raid 10 import

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

    ZFS directory empty after reboot

    If your ZFS pool become damaged then as your self why it may happen. ECC ram? ZFS configuration?
  12. N

    ZFS directory empty after reboot

    if all mountpoints is OK and all volumes are mounted then I don't know why your files are missing.
  13. N

    ZFS directory empty after reboot

    # zfs get mountpoint # zfs get mounted
  14. N

    ZFS Cache and Log disk Failure

    Log device is needed to check missing data on pool import action. If your Log device is crashed you can import pool manually by force .
  15. N

    PVE 5.2: ZFS "No space left on device" Avail 4,55T

    The error you think you hitted is more related to Linux kernel 3.x and may be older versions. Do this test # rm -rf SRC; mkdir SRC; for i in $(seq 1 10000); do echo $i > SRC/$i ; done; find SRC | wc -l #for i in $(seq 1 10); do cp -r SRC DST$i; find DST$i | wc -l; done

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!