Can you get us the process state dump of the glusterfs client where httpd is
hung? kill -USR1 will generate /tmp/glusterdump.pid which is
the dumpfile.
Avati
On Mon, Jun 13, 2011 at 2:18 PM, Jiri Lunacek wrote:
> Hi all.
>
> We have been having problems with hung tasks of apache reading from
>
hello.
do you maybe have already feedback?
was it successfull? (disabled io-cache, disabled stat-prefetch, inreades
io-thread count to 64)
is/was your problem similar to this one?
http://bugs.gluster.com/show_bug.cgi?id=3011
thx
christopher
Am 13.06.2011 19:14, schrieb Jiri Lunacek
hi James,
bricks 3-10 dont have problems, I think brick 01, 02 went to split brain
situation, could you confirm if you see the following logs in your mount's log
file
[afr-self-heal-metadata.c:524:afr_sh_metadata_fix]0-stress-volume-replicate-0:
Unable to self-heal permissions/ownership of '
Hi Pranith.
Here is the revised listing - please notice that bricks g01 and g02 on the two
servers (jc1letgfs14 and 15) have what appear to be "normal" trusted.afr
attributes, but the balance of the bricks (3-10) all have
=0x.
http://pastebin.com/j0hVFTzd
Is this right
Disable io-cache and up the threads to 64 and your problems should
disappear. They did for me when I made both of these changes.
Justice London
From: gluster-users-boun...@gluster.org
[mailto:gluster-users-boun...@gluster.org] On Behalf Of Jiri Lunacek
Sent: Monday, June 13, 2011 1:49 AM
To
On Mon, Jun 13, 2011 at 11:04:18AM +0100, Daniel Manser wrote:
> I disconnected the crossover (replication) link again and it
> happened again. When I re-connect it afterwards, it takes some
> seconds and Gluster NFS works again. If this behavior is normal,
> then the replication link becomes a sin
Hi Pranith.
Sorry - last week was a rough one. Disregard that pastebin - I will put up a
new one that makes more sense and repost to the list.
James
-Original Message-
From: Pranith Kumar. Karampuri [mailto:prani...@gluster.com]
Sent: Monday, June 13, 2011 1:12 AM
To: Burnash, James; Je
I disconnected the crossover (replication) link again and it happened
again. When I re-connect it afterwards, it takes some seconds and
Gluster NFS works again. If this behavior is normal, then the
replication link becomes a single point of failure. Any suggestions?
Hi all.
We have been having problems with hung tasks of apache reading from glusterfs
2-replica volume ever since upgrading to 3.2.0. The problems were identical to
those described here:
http://gluster.org/pipermail/gluster-users/2011-May/007697.html
Yesterday we updated to 3.2.1.
A good thin
