iscsi target and VMware/esxi timeouts

Hi, we are experimenting issues with several esxi’s servers that use freebsd 10.2 stable as a iscsi target. ie: Nov 11 17:58:16 store-07 kernel: WARNING: 132.65.11.201 (iqn.1998-01.com.vmware:pe-02-2fa7cd9e): no ping reply (NOP-Out) after 5 seconds; dropping connection Nov 11 17:58:16 store-07 k

Re: iscsi target and VMware/esxi timeouts

Hello, > Am 14.11.2017 um 10:08 schrieb Daniel Braniss : > > Hi, > we are experimenting issues with several esxi’s servers that use freebsd 10.2 > stable as a iscsi target. > ie: > Nov 11 17:58:16 store-07 kernel: WARNING: 132.65.11.201 > (iqn.1998-01.com.vmware:pe-02-2fa7cd9e): no ping reply (

Re: Panic in unionfs "it is not a unionfs-vnode"

Oops, wrong list. I just resent to freebsd-current. > On 15 Nov 2017, at 12:48, Jan Mikkelsen wrote: > > Hi, > > I got the panic below in unionfs. Head as at 325569, 2017-11-09 12:41:00 > +1100 (Thu, 09 Nov 2017). > > This is a ufs filesystem union mounted on top of a read-only ufs /etc. I kn

Panic in unionfs "it is not a unionfs-vnode"

Hi, I got the panic below in unionfs. Head as at 325569, 2017-11-09 12:41:00 +1100 (Thu, 09 Nov 2017). This is a ufs filesystem union mounted on top of a read-only ufs /etc. I know unionfs has "architecture issues”. Is this resolvable? panic: unionfs: it is not unionfs-vnode cpuid = 5 time =