Date: Mon, 17 Feb 2020 10:47:29 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 235856] FreeBSD freezes on AWS EC2 t3 machines Message-ID: <bug-235856-27103-VaInQC9TWb@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-235856-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-235856-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235856 --- Comment #18 from mail@rubenvos.com --- Hi Colin, > 1. How repeatable is this? Does it happen to every instance you launch (= after a variable number of days)? Unfortunately we are not in the habit of often redeplying our zfs nodes (si= nce they provide storage for whole platforms) :( It still happens to the affect= ed nodes though: bzgrep "nvme1: Missing interrupt" /var/log/messages.0.bz2 ; grep "nvme1: Missing interrupt" /var/log/messages Nov 16 03:04:18 zfs01 kernel: nvme1: Missing interrupt Nov 16 03:05:19 zfs01 kernel: nvme1: Missing interrupt Nov 25 03:04:36 zfs01 kernel: nvme1: Missing interrupt Nov 25 03:05:07 zfs01 kernel: nvme1: Missing interrupt Nov 25 03:06:07 zfs01 kernel: nvme1: Missing interrupt Dec 13 03:04:34 zfs01 kernel: nvme1: Missing interrupt Dec 13 03:05:35 zfs01 kernel: nvme1: Missing interrupt Dec 13 03:06:26 zfs01 kernel: nvme1: Missing interrupt Dec 13 03:06:57 zfs01 kernel: nvme1: Missing interrupt Dec 13 03:07:58 zfs01 kernel: nvme1: Missing interrupt Jan 25 03:06:02 zfs01 kernel: nvme1: Missing interrupt Jan 25 03:07:02 zfs01 kernel: nvme1: Missing interrupt Feb 11 03:05:32 zfs01 kernel: nvme1: Missing interrupt Feb 11 03:07:01 zfs01 kernel: nvme1: Missing interrupt Feb 17 03:06:29 zfs01 kernel: nvme1: Missing interrupt =3D=3D=3D bzgrep "nvme1: Missing interrupt" /var/log/messages.0.bz2 ; grep "nvme1: Missing interrupt" /var/log/messages Jan 25 04:29:03 volume3 kernel: nvme1: Missing interrupt Feb 4 04:04:45 volume3 kernel: nvme1: Missing interrupt Feb 11 04:04:48 volume3 kernel: nvme1: Missing interrupt Kind of interesting that zfs01 and volume03 have totally different customer= s, usage patterns but have a collission of 2 dates :|=20 > 2. Have you tried different instance types? Yes. This issue is not manifesting itself on an r4.xlarge instance. Same am= i on r5.large: problems... > 3. What sort of disk is this? We use cloudformation/ansible to deploy these servers, so they are all kind= of identically configured (apart from sizing). Both instances suffering from = this issue are 500GB+ EBS GP2 or IO disks with GPT and a zpool configured onto t= hem.=20 Please let me know if you would like to receive more information. Kind regards, Ruben --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-235856-27103-VaInQC9TWb>