On Mon, Jul 30, 2018 at 1:03 AM mabi wrote:
> Hi,
>
> I just noticed that when I run a "systemctl stop glusterfs" on Debian 9
> the following glustereventsd processes are still running:
>
> root 2471 1 0 22:03 ?00:00:00 python
> /usr/sbin/glustereventsd --pid-file
Hi,
I just noticed that when I run a "systemctl stop glusterfs" on Debian 9 the
following glustereventsd processes are still running:
root 2471 1 0 22:03 ?00:00:00 python /usr/sbin/glustereventsd
--pid-file /var/run/glustereventsd.pid
root 2489 2471 0 22:03 ?
Hi All,
We are adding a new brick (91TB) to our existing gluster volume (328
TB). The new brick is on a new physical server and we want to make sure
that we are doing this correctly (the existing volume had 2 bricks on a
single physical server). Both are running glusterfs 3.7.11. The steps