[SOLVED] glusterfs mount

liska_

Member
Nov 19, 2013
115
3
18
Hello,
I have a problem mounting glusterfs on one of my server in cluster. On one node it is mounted without any problem but on the other one I can find this messages in syslog
cluster3 pvestatd[558285]: WARNING: unable to activate storage 'zalohysun' - directory '/mnt/pve/zalohysun' does not exist
cluster3 pvedaemon[558262]: WARNING: unable to activate storage 'zalohysun' - directory '/mnt/pve/zalohysun' does not exist

I tried a few configurations of gluster and before any change I removed gluster from proxmox and than I added it again. I can see it using command mount, but df hangs up as well as tryin to list /mnt/pve directory. Interesting thing is that GUI stops responding and in logs I can see
cluster3 pveproxy[557215]: WARNING: proxy detected vanished client connection .
When I remove it from /etc/pve/storage.cfg and unmount it using umount -l it starts working again. Restarting pvestatd or pvedaemon does not help. I have the same experience when using probably faulty nfs server.

pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-24 (running version: 3.1-24/060bd5a6)
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-9
libpve-access-control: 3.0-8
libpve-storage-perl: 3.0-18
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1
 
Last edited:
make sure your network works properly, then try mounting gluster by hand. when that works, go to gui.
 
Hi jinjer,
thanks a lot for your answer, it gave me a hint where to find a problem - in gluster logs and not in proxmox logs.
I was trying to use a separate network for syncing between file servers and the problematic proxmox server did not have access to this network.
This time I connected gluster servers through domain names instead of ips and change /etc/hosts on my servers so it is now possible to use different network for access and syncing.
Thanks a lot!
 

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!