Hello,
I wanted to report that I had this morning a similar issue on another server
where a few PHP-FPM processes get blocked on different GlusterFS volume mounted
through a FUSE mount. This GlusterFS volume has no quota enabled so it might
not be quota related after all.
Here would be the
On Tue, Aug 14, 2018 at 7:23 PM, mabi wrote:
> Bad news: the process blocked happened again this time with another
> directory of another user which is NOT over his quota but which also has
> quota enabled.
>
> The symptoms on the Linux side are the same:
>
> [Tue Aug 14 15:30:33 2018] INFO:
Bad news: the process blocked happened again this time with another directory
of another user which is NOT over his quota but which also has quota enabled.
The symptoms on the Linux side are the same:
[Tue Aug 14 15:30:33 2018] INFO: task php5-fpm:14773 blocked for more than 120
seconds.
[Tue
Thanks for letting us know. Sanoj, can you take a look at this?
Thanks.
Nithya
On 14 August 2018 at 13:58, mabi wrote:
> As you mentioned after creating the /var/run/gluster directory I got a
> statedump file in there.
>
> As a workaround I have now removed the quota for this specific
As you mentioned after creating the /var/run/gluster directory I got a
statedump file in there.
As a workaround I have now removed the quota for this specific directory and as
it is a production server I can currently not "play" with it by adding the
quota back and having the same problem as
On 9 August 2018 at 19:54, mabi wrote:
> 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
>
>
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
12 matches
Mail list logo
