FYI, I tracked this down to the cluster/ha translator. If I remove it,
the problem goes away; if I add it back, the problem comes back.
Thanks,
Brent
On Wed, 24 Jun 2009, Brent A Nelson wrote:
At least with 2.0.2, my GlusterFS filesystems
(io-threads=>distribute=>replicate=>ha=>client=>serv
On Wed, 24 Jun 2009 15:45:40 +0100, Vidar Hokstad
wrote:
> On Wed, Jun 24, 2009 at 11:28 AM, Gordan Bobic wrote:
>
>>
>> What version of fuse are you running? I have found a number of heisenbug
>> issues arising from using mismatched fuse versions, and installing
>> glusterfs patched fuse (2.7.4
At least with 2.0.2, my GlusterFS filesystems
(io-threads=>distribute=>replicate=>ha=>client=>server=>io-threads=>posix-locks=>posix)
seem to have a serious problem with file renaming:
r...@node1:/data# mkdir test
r...@node1:/data# cd test
r...@node1:/data/test# cp /bin/ls .
r...@node1:/data/te
On Wed, Jun 24, 2009 at 11:28 AM, Gordan Bobic wrote:
>
> What version of fuse are you running? I have found a number of heisenbug
> issues arising from using mismatched fuse versions, and installing
> glusterfs patched fuse (2.7.4glfs11 last time I checked) made most of those
> problems go away.
On Wed, Jun 24, 2009 at 10:39 AM, Vikas Gorur wrote:
> Thanks for all the info. Could you create a new bug on our Bugzilla
> (http://bugs.gluster.com/) and paste the same info there too? That
> way we can keep track of the issue if it ever pops up in our testing
> and you can get an update when i
On Wed, 24 Jun 2009 10:30:54 +0100, Vidar Hokstad
wrote:
> See below for what I'm currently running. I'm testing without readahead
at
> the moment - I haven't seen it fail with it commented out so far, but
it's
> too early to tell.
>
> Before I added the trace translator the error rate was much h
On Wed, 24 Jun 2009 09:45:54 +0100, Vidar Hokstad
wrote:
> Hi,
> I have a cluster set up with 2.0.1, and when under heavy load I keep
> getting
> files that are getting cut off in the middle (cat [problematic file] on
the
> client will give different/shorter output than doing the same on the
> ser
On Wed, 24 Jun 2009 10:36:26 +0200, Mateusz Korniak
wrote:
> Hi,
> Simple scenario, server serves directory to client
> After some time clinet is not able to dir, df (any I/O operation blocking
> forever)
>
>
> Reset of server glusterfsd does not help, signalling --TERM/ --KILL on
> client
>
- "Vidar Hokstad" wrote:
> See below for what I'm currently running. I'm testing without
> readahead at
> the moment - I haven't seen it fail with it commented out so far, but
> it's
> too early to tell.
>
> Before I added the trace translator the error rate was much higher.
> After I
> add
See below for what I'm currently running. I'm testing without readahead at
the moment - I haven't seen it fail with it commented out so far, but it's
too early to tell.
Before I added the trace translator the error rate was much higher. After I
added it, it took several hours before it started fai
- "Vidar Hokstad" wrote:
What is your client configuration? Do you have a way to reproduce this?
Vikas
--
Engineer - http://gluster.com/
A: Because it messes up the way people read text.
Q: Why is a top-posting such a bad thing?
--
___
Gluster
Hi,
I have a cluster set up with 2.0.1, and when under heavy load I keep getting
files that are getting cut off in the middle (cat [problematic file] on the
client will give different/shorter output than doing the same on the server)
When I unmount and mount the client volume again it works fine fo
Hi,
Simple scenario, server serves directory to client
After some time clinet is not able to dir, df (any I/O operation blocking
forever)
Reset of server glusterfsd does not help, signalling --TERM/ --KILL on client
side glustefs process either,
I am unable to umount:
[mat...@client ~]$ sudo
- "nicolas prochazka" wrote:
> Hello guys,
> I'm trying some tests with glusterfs 2.0.2 and postgresql , i obtain
> :
> org.postgresql.util.PSQLException: ERROR: could not seek to end of
> segment 0 of relation 1663/16384/1259: Input/output error
>
> Configuration of gluster is very simple,
Hello guys,
I'm trying some tests with glusterfs 2.0.2 and postgresql , i obtain :
org.postgresql.util.PSQLException: ERROR: could not seek to end of
segment 0 of relation 1663/16384/1259: Input/output error
Configuration of gluster is very simple, AFR mode with only two
server. Performance Xlator
15 matches
Mail list logo
