Hi Strahil
I have tried a couple of tests of trying to gunzip the file with top
running on the client (mseas) and on the brick server (mseas-data3) and
with iotop running on the client (mseas). I was not able to install
iotop on the brick server yet (the external line is down). I'll repeat
Hi Strahil,
I poked around our logs, and found this on the front-end (from the day &
time of the last time we had the issue)
Jun 15 10:51:17 mseas gdata[155485]: [2022-06-15 14:51:17.263858] C
[rpc-clnt-ping.c:165:rpc_clnt_ping_timer_expired]
0-data-volume-client-2: server
Hi Strahil,
I poked around again and for brick 3 (where the file we were testing
resides) I only found the same log file as was at the bottom of my
first Email:
---
mseas-data3: bricks/export-sda-brick3.log
On Wed, Jun 15, 2022 at 6:28 PM Pat Haley wrote:
>
> Hi,
>
> We have a cluster whose common storage is a gluster volume consisting of 5
> bricks residing on 3 servers.
>
>- Gluster volume machines
> - mseas-data2: CentOS release 6.8 (Final)
> - mseas-data3: CentOS release 6.10
