[Gluster-users] VM disks corruption on 3.7.11
lemonnierk at ulrar.net
Thu May 12 14:03:02 UTC 2016
I had a problem some time ago with 3.7.6 and freezing during heals,
and multiple persons advised to use 3.7.11 instead. Indeed, with that
version the freez problem is fixed, it works like a dream ! You can
almost not tell that a node is down or healing, everything keeps working
except for a little freez when the node just went down and I assume
hasn't timed out yet, but that's fine.
Now I have a 3.7.11 volume on 3 nodes for testing, and the VM are proxmox
VMs with qCow2 disks stored on the gluster volume.
Here is the config :
Volume Name: gluster
Volume ID: e4f01509-beaf-447d-821f-957cc5c20c0a
Number of Bricks: 1 x 3 = 3
As mentioned, I rebooted one of the nodes to test the freezing issue I had
on previous versions and appart from the initial timeout, nothing, the website
hosted on the VMs keeps working like a charm even during heal.
Since it's testing, there isn't any load on it though, and I just tried to refresh
the database by importing the production one on the two MySQL VMs, and both of them
started doing I/O errors. I tried shutting them down and powering them on again,
but same thing, even starting full heals by hand doesn't solve the problem, the disks are
corrupted. They still work, but sometimes they remount their partitions read only ..
I believe there is a few people already using 3.7.11, no one noticed corruption problems ?
Anyone using Proxmox ? As already mentionned in multiple other threads on this mailing list
by other users, I also have pretty much always shards in heal info, but nothing "stuck" there,
they always go away in a few seconds getting replaced by other shards.
PGP Fingerprint : 89A5 2283 04A0 E6E9 0111
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: Digital signature
More information about the Gluster-users