On Wed, Aug 12, 2020 at 2:25 AM wrote:
> While trying to diagnose an issue with a set of VMs that get stopped for
> I/O problems at startup, I try to deal with the fact that their boot disks
> cause this issue, no matter where I connect them. They might have been the
> first disks I ever tried
Gluster log level (both volume and brick) can be done by following
Can you test with a fresh (blank template) VM:
- create a test VM
- create snapshot
- delete snapshot
Hi Strahil, no updates, especially since I am stuck on 4.3.11 and they tell us
Glusterfs is 6.9-1.el7.
Apart from those three VMs and the inability to copy disks the whole farm runs
fine so far.
Where would I configure the verbosity of logging? Can't find an obvious config
Sounds like the gluster ACL bug.
Did you recently patchbyour gluster ?
Did you test functionality of oVirt after gluster upgrade?
Check the brick logs for errors mentioning 'acl' (you might need to increase
log level temporarily).
If you do brick log reporting issues related to acl - you can
Mail list logo