Hey Prasanna,
Thanks for your help! One of the issues we've had is DD doesn't seem to
reproduce it. Anything that logs and handles large volumes, think mail and web
servers, tends to segfault the most frequently. I could write up a load test
and we could put apache on it and try that as that's
Hi Josh Boon,
Below are my setup details:
# qemu-system-x86_64 --version
QEMU emulator
On 07/29/2015 06:56 PM, Pranith Kumar Karampuri wrote:
On 07/29/2015 06:10 PM, Emmanuel Dreyfus wrote:
On Wed, Jul 29, 2015 at 04:06:43PM +0530, Vijay Bellur wrote:
- If there are tests that cannot be fixed easily in the near term,
we move
such tests to a different folder or drop such test
On 07/29/2015 06:10 PM, Emmanuel Dreyfus wrote:
On Wed, Jul 29, 2015 at 04:06:43PM +0530, Vijay Bellur wrote:
- If there are tests that cannot be fixed easily in the near term, we move
such tests to a different folder or drop such test units.
A tests/disabled directory seemsthe way to go. But
Thank you to eveyone who took part in the meeting. Today's meeting
finished exactly on time and we covered a lot of topics.
I've added the links to the meeting logs and the meeting summary to
the end of this mail.
As always, the next community meeting will be on next Wednesday
1200UTC in #gluster
On Wed, Jul 29, 2015 at 04:06:43PM +0530, Vijay Bellur wrote:
> - If there are tests that cannot be fixed easily in the near term, we move
> such tests to a different folder or drop such test units.
A tests/disabled directory seemsthe way to go. But before going there,
the test maintaniner should
I have updated tiering related spurious failures to proper state.
Regards
Rafi KC
On 07/29/2015 03:40 PM, Pranith Kumar Karampuri wrote:
> hi,
> I just updated
> https://public.pad.fsfe.org/p/gluster-spurious-failures with the
> latest spurious failures we saw in linux and NetBSD regressions.
On Wednesday 29 July 2015 03:40 PM, Pranith Kumar Karampuri wrote:
hi,
I just updated
https://public.pad.fsfe.org/p/gluster-spurious-failures with the latest
spurious failures we saw in linux and NetBSD regressions. Could you guys
update with any more spurious regressions that you guys are o
Hi all,
The weekly Gluster community meeting will be starting in
#gluster-meeting on Freenode at 12UTC (~90 minutes from now).
Agenda: https://public.pad.fsfe.org/p/gluster-community-meetings
Current Agenda topics are:
- Last week's action items
- Gluster 3.7
- Gluster 3.6
- Gluster 3.5
- Gluste
On 07/27/2015 08:30 PM, Glomski, Patrick wrote:
I built a patched version of 3.6.4 and the problem does seem to be
fixed on a test server/client when I mounted with those flags (acl,
resolve-gids, and gid-timeout). Seeing as it was a test system, I
can't really provide anything meaningful as to
hi,
I just updated
https://public.pad.fsfe.org/p/gluster-spurious-failures with the latest
spurious failures we saw in linux and NetBSD regressions. Could you guys
update with any more spurious regressions that you guys are observing
but not listed on the pad. Could you guys help in fixing
11 matches
Mail list logo