I added a new 1TB SSD to my cache pool and for the last day or so my server has been battling to run a parity check at the same time as normal mover activity, taking a day and a half to complete 60%.  With my old cache pool my array could handle doing a parity check at the same time as normal mover activity.

 

This morning I woke up to frozen dockers.  I've had problems with unresponsive dockers in the past which never got resolved, but I'd learnt to live with it and things seemed a bit better in 6.6.

 

 

Anybody got any idea what's gone wrong now?

 

Thanks in advance.

 

highlander-diagnostics-20180927-0849.zip

 

Not sure if related but there are a lot of errors like these:

 

Sep 26 18:19:16 Highlander kernel: DMAR: [DMA Write] Request device [08:00.0] fault addr 20d61d000 [fault reason 02] Present bit in context entry is clear
Sep 26 18:19:18 Highlander kernel: DMAR: DRHD: handling fault status reg 2
Sep 26 18:19:18 Highlander kernel: DMAR: [DMA Write] Request device [08:00.0] fault addr 20d61d000 [fault reason 02] Present bit in context entry is clear
Sep 26 18:19:20 Highlander kernel: DMAR: DRHD: handling fault status reg 102
Sep 26 18:19:20 Highlander kernel: DMAR: [DMA Write] Request device [08:00.0] fault addr 20d61d000 [fault reason 02] Present bit in context entry is clear
Sep 26 18:19:22 Highlander kernel: DMAR: DRHD: handling fault status reg 202

Device 08:00.0 is:

 

08:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242]
    Subsystem: ASUSTeK Computer Inc. ASM1142 USB 3.1 Host Controller [1043:8675]
    Kernel driver in use: vfio-pci

There are also a lot of likely related USB disconnect errors, so if possible avoid using this USB controller.

15 minutes ago, johnnie.black said:

Not sure if related but there are a lot of errors like these:

 

Sep 26 18:19:16 Highlander kernel: DMAR: [DMA Write] Request device [08:00.0] fault addr 20d61d000 [fault reason 02] Present bit in context entry is clear
Sep 26 18:19:18 Highlander kernel: DMAR: DRHD: handling fault status reg 2
Sep 26 18:19:18 Highlander kernel: DMAR: [DMA Write] Request device [08:00.0] fault addr 20d61d000 [fault reason 02] Present bit in context entry is clear
Sep 26 18:19:20 Highlander kernel: DMAR: DRHD: handling fault status reg 102
Sep 26 18:19:20 Highlander kernel: DMAR: [DMA Write] Request device [08:00.0] fault addr 20d61d000 [fault reason 02] Present bit in context entry is clear
Sep 26 18:19:22 Highlander kernel: DMAR: DRHD: handling fault status reg 202

Device 08:00.0 is:

 

08:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242]
    Subsystem: ASUSTeK Computer Inc. ASM1142 USB 3.1 Host Controller [1043:8675]
    Kernel driver in use: vfio-pci

There are also a lot of likely related USB disconnect errors, so if possible avoid using this USB controller.

Thanks for spotting this, which probably ties with the additional background info I was about to add to my post.

 

As I rebooted I realised I forgot to add that I updated my bios.  When redoing my bios settings I spotted an 'enable USB 3.1 charging support' option for that controller which I added - I've now turned it off.

 

The only other change I made in the bios was I changed the secure boot support from Windows UEFI to 'other os' which made sense to me, but I've put it back to Windows.

 

Let's see if the USB bios setting was the culprit.