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 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 kernel: WARNING: 132.65.11.205 (iqn.1998-01.com.vmware:pe-03-13e8b52d): no ping reply (NOP-Out) after 5 seconds; dropping connection Nov 11 17:58:17 store-07 kernel: WARNING: 132.65.11.203 (iqn.1998-01.com.vmware:pe-13-60e87d06): no ping reply (NOP-Out) after 5 seconds; dropping connection Nov 11 17:58:17 store-07 kernel: WARNING: 132.65.11.205 (iqn.1998-01.com.vmware:pe-03-13e8b52d): no ping reply (NOP-Out) after 5 seconds; dropping connection these are 3 different esxis that almost at the same time the target looses connection to the initiators. at the moment most ‘clients’ recover from the scsi error, but older freebsds don’t. in any case, increasing the timeout is not helping. any clues are welcome :-) over the weekend i’m planning to upgrade the target to 11.1 and take for the hills. danny ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
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 (NOP-Out) after 5 > seconds; dropping connection > 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 kernel: WARNING: 132.65.11.205 > (iqn.1998-01.com.vmware:pe-03-13e8b52d): no ping reply (NOP-Out) after 5 > seconds; dropping connection > Nov 11 17:58:17 store-07 kernel: WARNING: 132.65.11.203 > (iqn.1998-01.com.vmware:pe-13-60e87d06): no ping reply (NOP-Out) after 5 > seconds; dropping connection > Nov 11 17:58:17 store-07 kernel: WARNING: 132.65.11.205 > (iqn.1998-01.com.vmware:pe-03-13e8b52d): no ping reply (NOP-Out) after 5 > seconds; dropping connection > > these are 3 different esxis that almost at the same time the target looses > connection to the initiators. > at the moment most ‘clients’ recover from the scsi error, but older freebsds > don’t. > > in any case, increasing the timeout is not helping. > > any clues are welcome :-) > > over the weekend i’m planning to upgrade the target to 11.1 and take for the > hills. Are you using istgt or ctld? We have did experience similar occasional problems with the former but never with the latter. Patrick -- punkt.de GmbH Internet - Dienstleistungen - Beratung Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100 76133 Karlsruhe i...@punkt.de http://punkt.de AG Mannheim 108285 Gf: Juergen Egeling ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
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 know > unionfs has "architecture issues”. Is this resolvable? > > panic: unionfs: it is not unionfs-vnode > cpuid = 5 > time = 1510678800 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe02c418c280 > vpanic() at vpanic+0x19c/frame 0xfe02c418c300 > kassert_panic() at kassert_panic+0x126/frame 0xfe02c418c370 > unionfs_lock() at unionfs_lock+0x635/frame 0xfe02c418c400 > VOP_LOCK1_APV() at VOP_LOCK1_APV+0xd9/frame 0xfe02c418c430 > _vn_lock() at _vn_lock+0x66/frame 0xfe02c418c4a0 > vget() at vget+0x82/frame 0xfe02c418c4e0 > cache_lookup() at cache_lookup+0x787/frame 0xfe02c418c5c0 > vfs_cache_lookup() at vfs_cache_lookup+0xac/frame 0xfe02c418c620 > VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0xd3/frame 0xfe02c418c650 > lookup() at lookup+0x682/frame 0xfe02c418c6f0 > namei() at namei+0x51a/frame 0xfe02c418c7b0 > kern_statat() at kern_statat+0x98/frame 0xfe02c418c9c0 > sys_fstatat() at sys_fstatat+0x2f/frame 0xfe02c418cac0 > amd64_syscall() at amd64_syscall+0x79b/frame 0xfe02c418cbf0 > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfe02c418cbf0 > --- syscall (552, FreeBSD ELF64, sys_fstatat), rip = 0x800dd48da, rsp = > 0x7fffddc8, rbp = 0x7fffde70 — > > > Thanks, > > Jan Mikkelsen > > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
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 = 1510678800 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe02c418c280 vpanic() at vpanic+0x19c/frame 0xfe02c418c300 kassert_panic() at kassert_panic+0x126/frame 0xfe02c418c370 unionfs_lock() at unionfs_lock+0x635/frame 0xfe02c418c400 VOP_LOCK1_APV() at VOP_LOCK1_APV+0xd9/frame 0xfe02c418c430 _vn_lock() at _vn_lock+0x66/frame 0xfe02c418c4a0 vget() at vget+0x82/frame 0xfe02c418c4e0 cache_lookup() at cache_lookup+0x787/frame 0xfe02c418c5c0 vfs_cache_lookup() at vfs_cache_lookup+0xac/frame 0xfe02c418c620 VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0xd3/frame 0xfe02c418c650 lookup() at lookup+0x682/frame 0xfe02c418c6f0 namei() at namei+0x51a/frame 0xfe02c418c7b0 kern_statat() at kern_statat+0x98/frame 0xfe02c418c9c0 sys_fstatat() at sys_fstatat+0x2f/frame 0xfe02c418cac0 amd64_syscall() at amd64_syscall+0x79b/frame 0xfe02c418cbf0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfe02c418cbf0 --- syscall (552, FreeBSD ELF64, sys_fstatat), rip = 0x800dd48da, rsp = 0x7fffddc8, rbp = 0x7fffde70 — Thanks, Jan Mikkelsen ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
