[PVE-User] inconsistency between rgmanager & pve status
Dietmar Maurer
dietmar at proxmox.com
Mon Oct 6 15:08:31 CEST 2014
> > ip1:/glusterstorage /glusterstorage glusterfs
> > defaults,noauto,_netdev,backup-volfile-servers=ip2:ip3
>
> OK, we use system mount command for glusterfs, so we run into same problem
> as with NFS - we get blocked by the operating system. I have no real idea how to
> avoid that.
Normally the system should simply use one of those backup-volfile-servers. But I also run into troubles with long timeouts, and backup-volfile-servers never worked reliable for me. We have a workaround in
latest code:
libpve-storage-perl (3.0-22) unstable; urgency=low
* glusterfs: new option server2 to specify backup volfile server
Please use /etc/pve/storage.cfg to configure glusterfs instead:
glusterfs: glusterstoreage
volume glusterstorage
path /glusterstorage
content images,iso,backup
server <server-ip>
server2 <backup-server-ip>
Does that help?
More information about the pve-user
mailing list