Trying to share ZFS storage between servers

obitori

Member
Jan 4, 2023
14
0
6
I have two proxmox servers (pvelab and pvelab2). I have working zfs storage on both, but cannot share them. The storage shows up in the other server's list but grayed out.

Screenshot from 2023-01-14 19-07-10.png

Code:
root@pvelab:/mnt/vmz1/images/101# cat /etc/pve/storage.cfg
dir: local
    path /var/lib/vz
    content backup,snippets
    shared 1

lvmthin: local-lvm
    thinpool data
    vgname pve
    content images,rootdir

dir: vmz24
    path /mnt/vmz24
    content rootdir,backup,images
    is_mountpoint yes
    nodes pvelab,pvelab2
    shared 1

dir: iso
    path /mnt/iso
    content iso,snippets,vztmpl
    is_mountpoint yes
    shared 1

dir: vmz1
    path /mnt/vmz1
    content images,rootdir,backup
    is_mountpoint yes
    shared 1

dir: vmz2
    path /mnt/vmz2
    content backup,rootdir,images
    is_mountpoint yes
    shared 1

dir: isoz
    path /mnt/isoz
    content iso,snippets,vztmpl
    is_mountpoint yes
    shared 1
 
Quick followup: Is it better to list the zfs pool as dir or zfspool? Not sure what the pros / cons are.
 
zfs is not cluster aware filesystem. if you force access from two servers you will corrupt data.
dir storage is completely unaware where its located, ie zfs/ext/ntfs or fat32. So if you configure it as "dir:" - it has nothing to do with zfs.
The table here shows what can and cant be a shared storage: https://pve.proxmox.com/wiki/Storage

In context of shared storage the is_mountpoint is only applicable to NFS or CIFS backed storage.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: obitori
zfs is not cluster aware filesystem. if you force access from two servers you will corrupt data.
dir storage is completely unaware where its located, ie zfs/ext/ntfs or fat32. So if you configure it as "dir:" - it has nothing to do with zfs.
The table here shows what can and cant be a shared storage: https://pve.proxmox.com/wiki/Storage

In context of shared storage the is_mountpoint is only applicable to NFS or CIFS backed storage.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Thank you! I'm reading up and experimenting with changes now.
 
zfs is not cluster aware filesystem. if you force access from two servers you will corrupt data.
dir storage is completely unaware where its located, ie zfs/ext/ntfs or fat32. So if you configure it as "dir:" - it has nothing to do with zfs.
The table here shows what can and cant be a shared storage: https://pve.proxmox.com/wiki/Storage

In context of shared storage the is_mountpoint is only applicable to NFS or CIFS backed storage.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
When you talk about "forcing access", does that include using NFS to share the pool with another server? Does a zfs pool shared as "dir" risk corruption. I'm new so not sure if you mean "adding share features" in /etc/pve/storage.cfg as "force sharing" or do you mean sharing a zfs drive via another means such as dir or nfs. Thanks for you help with this.
 

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!