Since it is recovering from it, maybe it is losing packets inside the network, what does "sar -n DEV" and "sar -n EDEV" look like during that time on both client seeing the pause and the server.
EDEV is typically all zeros unless something is lost. if something is being lost and it matches the times the time of hangs that could be it. On Mon, Oct 4, 2021 at 5:26 AM Terry Barnaby <ter...@beam.ltd.uk> wrote: > > and iostats: > > > 04/10/21 10:51:14 > avg-cpu: %user %nice %system %iowait %steal %idle > 2.09 0.00 1.56 0.02 0.00 96.33 > > Device r/s rkB/s rrqm/s %rrqm r_await rareq-sz w/s > wkB/s wrqm/s %wrqm w_await wareq-sz d/s dkB/s drqm/s %drqm > d_await dareq-sz f/s f_await aqu-sz %util > nvme0n1 0.00 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 0.00 > nvme1n1 0.00 0.00 0.00 0.00 0.00 0.00 7.10 > 39.20 1.40 16.47 1.68 5.52 0.00 0.00 0.00 0.00 > 0.00 0.00 0.10 1.00 0.01 0.19 > sda 0.00 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 0.00 > zram0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 0.00 > > > 04/10/21 10:51:40 > avg-cpu: %user %nice %system %iowait %steal %idle > 2.31 0.00 1.60 10.86 0.00 85.24 > > Device r/s rkB/s rrqm/s %rrqm r_await rareq-sz w/s > wkB/s wrqm/s %wrqm w_await wareq-sz d/s dkB/s drqm/s %drqm > d_await dareq-sz f/s f_await aqu-sz %util > nvme0n1 0.00 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 0.00 > nvme1n1 0.00 0.00 0.00 0.00 0.00 0.00 0.71 > 3.43 0.15 17.39 12.16 4.84 0.00 0.00 0.00 0.00 > 0.00 0.00 0.04 1.00 0.01 0.19 > sda 0.00 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 0.00 > zram0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 0.00 > > > 04/10/21 10:51:50 > avg-cpu: %user %nice %system %iowait %steal %idle > 2.59 0.00 1.69 0.17 0.00 95.55 > > Device r/s rkB/s rrqm/s %rrqm r_await rareq-sz w/s > wkB/s wrqm/s %wrqm w_await wareq-sz d/s dkB/s drqm/s %drqm > d_await dareq-sz f/s f_await aqu-sz %util > nvme0n1 0.00 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 0.00 > nvme1n1 0.00 0.00 0.00 0.00 0.00 0.00 1.40 > 11.20 1.40 50.00 12.36 8.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.20 1.00 0.02 0.50 > sda 0.00 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 0.00 > zram0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 > 0.00 0.00 0.00 0.00 0.00 0.00 > > So nothing obvious on the disks of the server. I am pretty sure this is an > NFS issue ... > > _______________________________________________ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
