Hi guys,
My use-case is somewhat unusual, so I thought I'd report these since
they may not get tripped under normal use. This is against 2.0.0rc1.
Setup is a shared root on GlusterFS/AFR with only one node (2nd node not
yet built).
Something weird seems to happen with some uses of ncurses
Another one - tail -f doesn't appear to work correctly for logs on
GlusterFS. The logs themselves seem to be OK (not corrupted), but tail
-f doesn't seem to properly list them incrementally, the output ends up
corrupted (missing lines, line breaks, etc). This was observed in the
case where
Heh our tests are kind of an unholy mess... but here's the part I think
is useful:
We use a startup script that will iterate through vol files and mount
the first available file on the list. We have a bunch of vol files that
test a few different server configurations. After mountpoints are
Hi Mickey,
Thanks for this.
Cheers,
Geoff Kassel.
On Mon, 9 Feb 2009, Mickey Mazarick wrote:
Heh our tests are kind of an unholy mess... but here's the part I think
is useful:
We use a startup script that will iterate through vol files and mount
the first available file on the list. We
2009/2/9 Gordan Bobic gor...@bobich.net:
I seem to have my gluster root daemon grown to 280MB, with no performance
translators. I'm hazarding a guess that this could be down to it's log
filesystem having been (re)moved. Is there a way to disable the logging
completely using a fstab parameter?
Nicolas,
You can get back to us if you still have the problem.
Krishna
2009/2/7 Cory Meyer cory.me...@gmail.com:
I ran into this same issue and should be fixed in
glusterfs--mainline--3.0--patch-899.
On Fri, Feb 6, 2009 at 6:12 AM, nicolas prochazka
prochazka.nico...@gmail.com wrote:
