On 05/05/2018 10:04 PM, Yanfei Wang wrote:
Hi,
https://docs.gluster.org/en/v3/Administrator%20Guide/arbiter-volumes-and-quorum/,
said,
```
There is a corner case even with replica 3 volumes where the file can
end up in a split-brain. AFR usually takes range locks for the
{offset, length} of
This is because of a new warning by liblvm2app. I have a hacky fix to the
compilation process to get rid of the warning. Please review:
https://github.com/gluster/glusterfs-patch-acceptance-tests/pull/130
However, this will soon become more than just a warning. We should either
fix this or
Shyam,
I know we've talked about this but I'm pretty sure this is going to
affect our release schedules.
Want to work with me tomorrow to see what we can do to make alternate ones?
- amye
On Sun, May 13, 2018 at 9:19 PM, Nigel Babu wrote:
> This is because of a new warning by
Hi,
Nigel pointed out that the nightly brick-mux tests are now failing for
about 11 weeks and we do not have a clear run of the same.
Spent some time on Friday collecting what tests failed and to an extent
why, and filed bug https://bugzilla.redhat.com/show_bug.cgi?id=1577672
Asks: Whoever has
Hi,
The builds are failing due to the following,
https://bugzilla.redhat.com/show_bug.cgi?id=1577668
Nigel/Misc, can you take a stab at finding out what is new that is
causing these warnings to appear?
Failing a quick resolution there, anyone from maintainers, could you
look at supressing the
[...truncated 6 lines...]
https://bugzilla.redhat.com/1571852 / build: Fails to build with libtirpc
https://bugzilla.redhat.com/1573226 / eventsapi: eventsapi: ABRT report for
package glusterfs has reached 10 occurrences
https://bugzilla.redhat.com/1576190 / fuse: RMAN backups to GFS is throwing