Search results

  1. P

    Use Proxmox Backup Server (PBS) 2.2-1 with Proxmox Virtual Environment 6.0-4

    Just a note, if you can upgrade to the latest PVE 6.x, the PBS storage option will appear and you can create your backup directly to the PBS server. Problems: - you need to upgrade your system to the 6.x, so, practically you need a backup before you upgrade :) - there is a change in mac address...
  2. P

    General backup thoughts - discussion starter

    Hello Everyone, This could be TL;DR I use Proxmox from the very beginning and I use ZFS for ages back when I had to compile it by myself and official PVE did not support using ZFS. I use smaller clusters (2 - 6 nodes, but a cluster is a cluster in case of 3+ nodes, so, if you see one, you saw...
  3. P

    Permission denied when trying to create ceph-osd on zvol

    Just an update, maybe still interesting for you: I got it working on my nodes, still under test phase. Here is the quick howto: https://forum.proxmox.com/threads/ceph-osd-on-zvol-or-dir.34727/#post-359969
  4. P

    Ceph OSD on zvol or dir?

    I just got it work with zvol. BIG FAT WARNING: DO NOT follow (copy-paste) these steps without knowledge of zfs, ceph and how to do research using google, otherwise you could easily destroy your existing cluster/data. Steps: - create snapshot for all your data in your zfs pools, just in case...
  5. P

    Ceph OSD on zvol or dir?

    Any update on this? Any workaround or plan? I also prefer zvol as osd disk instead of the whole disk. Please do not try to convince to use whole disk, because the question is how to use zvol instead of physical disk, not why use whole disk.... Thanks!
  6. P

    ProxMox VE 6 - replacing drive in zfs boot mirror

    In short: Yes, that's normal, because the 512M will be used for EFI boot as you can see. Other zfs disks with only 2 partitions "just" part of a pool, there are no reservation for any boot. Disklabel type: gpt Disk identifier: BDB522F2-A808-4C1F-8B7E-83E1CABD0D43 Device Start End...
  7. P

    Crash: /proc/sys/kernel/hung_task_timeout_secs - Problem mit ZFS?

    FYI: https://github.com/zfsonlinux/zfs/issues/8664
  8. P

    Proxmox V6 Servers freeze, Zvol blocked for more than 120s

    Update from Github: Here you can track the process of solving this issue by zfsonlinux itself: https://github.com/zfsonlinux/zfs/pull/9317
  9. P

    Proxmox V6 Servers freeze, Zvol blocked for more than 120s

    @bofh Thank you for your hint! I will check it next time. Regarding to my experience, these two servers were doing scrub, while zfs send/receive also happened between them on a 5 nodes cluster and there were about an hour difference. This was the 2nd or 3rd time. Even standalone servers froze in...
  10. P

    Proxmox V6 Servers freeze, Zvol blocked for more than 120s

    System No.2. It locked 3 times, so, definitely affected. Before: root@lm1:~# zpool status pool: rpool state: ONLINE scan: scrub repaired 0B in 0 days 01:08:43 with 0 errors on Sun Jul 14 01:32:44 2019 config: NAME STATE READ WRITE CKSUM...
  11. P

    Proxmox V6 Servers freeze, Zvol blocked for more than 120s

    In this system I did not experienced this kind of issue. This one has hard disks as pool and some ssd for log/zil. I will check my servers where the before situation still exists. This is the after: root@lm3:~# zpool status pool: rpool state: ONLINE scan: scrub canceled on Sun Sep 8...
  12. P

    Proxmox V6 Servers freeze, Zvol blocked for more than 120s

    @Stoiko Ivanov You are welcome :) I hope you can create a workaround patch and publish to the users as I think. Of course, zfs.conf should be checked before simply overwrite it ;)
  13. P

    Proxmox V6 Servers freeze, Zvol blocked for more than 120s

    @vanes thanks for the question, you are right. Steps: Check the actual setup: # cat /sys/module/zfs/parameters/zfs_vdev_scheduler It should be: noop Open or create new file if it does not exist using nano editor: # nano /etc/modprobe.d/zfs.conf Add or modify this line to contain the scheduler...
  14. P

    Proxmox V6 Servers freeze, Zvol blocked for more than 120s

    I got the following answer on github from Brian: So, we should try to set zfs_vdev_scheduler=none and check, does it work or not.
  15. P

    Proxmox V6 Servers freeze, Zvol blocked for more than 120s

    Rob, you found something on github:#8664 I report this thread to github.
  16. P

    Proxmox V6 Servers freeze, Zvol blocked for more than 120s

    Unfortunately the affected system will unresponsible, due to that, accessing disk blocked immediately, so, local log will contains nothing. I assume, there will be not so much in the remote log, too, because the syslog already printed to the screen and there will be not so much resource to run...
  17. P

    Crash: /proc/sys/kernel/hung_task_timeout_secs - Problem mit ZFS?

    Es ist genau das gleiche: https://forum.proxmox.com/threads/proxmox-v6-servers-freeze-zvol-blocked-for-more-than-120s.57765/
  18. P

    5.4 to 6 update : server hangs

    It could be related to this situation: https://forum.proxmox.com/threads/proxmox-v6-servers-freeze-zvol-blocked-for-more-than-120s.57765/
  19. P

    Proxmox V6 Servers freeze, Zvol blocked for more than 120s

    It seems I run into the same situation as you. Unfortunately I experienced this issue with 6 different servers (HP, Dell, Fujitsu and Intel servers). All of them use almost the same configuration as storage: rpool (and production storage) on SSD rpools are: raidz10 (4 SSDs); raidz2 (4 and other...
  20. P

    5.4 to 6 update : server hangs

    Do you use zfs as filesystem?