I'm running Proxmox 4.4-24 with all current updates and having a problem with nightly backups to a GlusterFS. It has run fine for over a year with no errors and good write speed. Backups are fast. In the past week they started failing with the following error:
"INFO: lzop: Read-only file system: <stdout>"
I think I've seen this before and the fix was to restart the GlusterFS but now I've tried everything and can't get it to work. On the command line I can create new files and delete in the filesystem so it's not really read-only. I've noticed access is now superslow, under 10Mb/s. Even listing the files on the filesystem runs terribly slow. It acts like a disk is going bad but they are not reporting any error and smart diags pass. I'm not sure what to do next. Anyone have a suggestion?
====================================
proxmox-ve: 4.4-112 (running kernel: 4.4.134-1-pve)
pve-manager: 4.4-24 (running version: 4.4-24/08ba4d2d)
pve-kernel-4.4.117-1-pve: 4.4.117-109
pve-kernel-4.4.134-1-pve: 4.4.134-112
pve-kernel-4.4.128-1-pve: 4.4.128-111
pve-kernel-4.4.114-1-pve: 4.4.114-108
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+2
libqb0: 1.0.1-1
pve-cluster: 4.0-55
qemu-server: 4.0-115
pve-firmware: 1.1-12
libpve-common-perl: 4.0-96
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.9.1-9~pve4
pve-container: 1.0-106
pve-firewall: 2.0-33
pve-ha-manager: 1.0-41
ksm-control-daemon: 1.2-1
glusterfs-client: 3.11.3-2
lxc-pve: 2.0.7-4
lxcfs: 2.0.8-2~pve4
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.9-pve15~bpo80
ceph: 10.2.11-1~bpo80+1
"INFO: lzop: Read-only file system: <stdout>"
I think I've seen this before and the fix was to restart the GlusterFS but now I've tried everything and can't get it to work. On the command line I can create new files and delete in the filesystem so it's not really read-only. I've noticed access is now superslow, under 10Mb/s. Even listing the files on the filesystem runs terribly slow. It acts like a disk is going bad but they are not reporting any error and smart diags pass. I'm not sure what to do next. Anyone have a suggestion?
====================================
proxmox-ve: 4.4-112 (running kernel: 4.4.134-1-pve)
pve-manager: 4.4-24 (running version: 4.4-24/08ba4d2d)
pve-kernel-4.4.117-1-pve: 4.4.117-109
pve-kernel-4.4.134-1-pve: 4.4.134-112
pve-kernel-4.4.128-1-pve: 4.4.128-111
pve-kernel-4.4.114-1-pve: 4.4.114-108
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+2
libqb0: 1.0.1-1
pve-cluster: 4.0-55
qemu-server: 4.0-115
pve-firmware: 1.1-12
libpve-common-perl: 4.0-96
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.9.1-9~pve4
pve-container: 1.0-106
pve-firewall: 2.0-33
pve-ha-manager: 1.0-41
ksm-control-daemon: 1.2-1
glusterfs-client: 3.11.3-2
lxc-pve: 2.0.7-4
lxcfs: 2.0.8-2~pve4
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.9-pve15~bpo80
ceph: 10.2.11-1~bpo80+1