Re: port-xen/54273: "zpool create pool xbd2" panics DOMU kernel

[Jarle Greipsland <jarle.greipsland%norid.no@localhost>]

The following reply was made to PR port-xen/54273; it has been noted by GNATS.

From: Jarle Greipsland <jarle.greipsland%norid.no@localhost>
To: gnats-bugs%netbsd.org@localhost, hannken%eis.cs.tu-bs.de@localhost
Cc: 
Subject: Re: port-xen/54273: "zpool create pool xbd2" panics DOMU kernel
Date: Sat, 08 Jun 2019 16:34:55 +0200 (CEST)

 "J. Hannken-Illjes" <hannken%eis.cs.tu-bs.de@localhost> writes:
 >  Looks like a MAXPHYS issue, please try the attached diff.
 [ ... ]
 The diff seems to have fixed the zpool problem.  I can now create
 a zfs pool.
 
 After having created the standard /pool zfs pool with xbd2 as the
 only device, I ran some zpool list, zpool status and other
 investigative commands.  I also ran a few zfs list/get commands,
 but without having done a 'zfs create'.  Then I left the system
 idle for a while, and it panicked.
 
 Console log:
 
 login: Jun  8 11:41:08 vm-2129 su: jarle to root on /dev/pts/0
 [ 15395.0600864] SLOW IO: zio timestamp 14390060087922ns, delta 1004999998514ns, last io 93740092365nspanic: I/O to pool 'pool' appears to be hung on vdev guid 4517737902492308706 at '/dev/xbd2'.
 [ 15395.0600864] cpu0: Begin traceback...
 [ 15395.0600864] vpanic() at netbsd:vpanic+0x143
 [ 15395.0600864] snprintf() at netbsd:snprintf
 [ 15395.0600864] vdev_cache_offset_compare() at zfs:vdev_cache_offset_compare
 [ 15395.0600864] vdev_deadman() at zfs:vdev_deadman+0x31
 [ 15395.0600864] spa_deadman_wq() at zfs:spa_deadman_wq+0xe2
 [ 15395.0600864] workqueue_worker() at netbsd:workqueue_worker+0xce
 [ 15395.0600864] cpu0: End traceback...
 
 [ 15395.0600864] dumping to dev 142,17 (offset=4194303, size=0): not possible
 [ 15395.0600864] rebooting...
 
 					-jarle