great
then its time to move to 4.1 then.
-wk
On 8/8/2018 5:05 AM, Amye Scavarda wrote:
Release Schedule will always have your back on this,
http://gluster.org/release-schedule -- I'll go update the /install page.
Thanks for the reminder!
On Tue, Aug 7, 2018 at 12:06 AM wkmail
Thanks for the documentation. On my client using FUSE mount I found the PID by
using ps (output below):
root 456 1 4 14:17 ?00:05:15 /usr/sbin/glusterfs
--volfile-server=gfs1a --volfile-id=myvol-private /mnt/myvol-private
Then I ran the following command
sudo kill -USR1 456
On Thu, Aug 9, 2018 at 6:47 PM, mabi wrote:
> Hi Nithya,
>
> Thanks for the fast answer. Here the additional info:
>
> 1. gluster volume info
>
> Volume Name: myvol-private
> Type: Replicate
> Volume ID: e7a40a1b-45c9-4d3c-bb19-0c59b4eceec5
> Status: Started
> Snapshot Count: 0
> Number of
A while back we found an issue with PHP around file locks.
https://bugs.php.net/bug.php?id=53076
This would leave hanging processes that we could only kill by forcibly
remounting the filesystems.
Its not really a PHP bug but they are not willing to fix the code to
deal with Glusters
Hi Nithya,
Thanks for the fast answer. Here the additional info:
1. gluster volume info
Volume Name: myvol-private
Type: Replicate
Volume ID: e7a40a1b-45c9-4d3c-bb19-0c59b4eceec5
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x (2 + 1) = 3
Transport-type: tcp
Bricks:
Brick1:
Hi,
Please provide the following:
1. gluster volume info
2. statedump of the fuse process when it hangs
Thanks,
Nithya
On 9 August 2018 at 18:24, mabi wrote:
> Hello,
>
> I recently upgraded my GlusterFS replica 2+1 (aribter) to version 3.12.12
> and now I see a weird behaviour on my
Hello,
I recently upgraded my GlusterFS replica 2+1 (aribter) to version 3.12.12 and
now I see a weird behaviour on my client (using FUSE mount) where I have
processes (PHP 5.6 FPM) trying to access a specific directory and then the
process blocks. I can't kill the process either, not even
