zfs locking vs vnode locking [Was: zfs/vfs lockups, via poudriere]

2014-11-24 Thread Andriy Gapon
On 23/11/2014 18:57, Sean Bruno wrote: 31071 100995 rm -mi_switch+0xe1 sleepq_wait+0x3a sleeplk+0x18d __lockmgr_args+0x9ab vop_stdlock+0x3c VOP_LOCK1_APV+0xab _vn_lock+0x43 zfs_lookup+0x45d zfs_freebsd_lookup+0x6d VOP_CACHEDLOOKUP_APV+0xa1 vfs_cache_lookup+0xd6

Re: zfs/vfs lockups, via poudriere

2014-11-23 Thread Sean Bruno
On Sun, 2014-11-23 at 00:09 +0200, Andriy Gapon wrote: On 22/11/2014 21:20, Sean Bruno wrote: bdrewery reported a vfs/zfs condition where operations will stall out and block (rm, mv, file) during a poudriere build. I've hit this now and it seems to be alleviated by setting

zfs/vfs lockups, via poudriere

2014-11-22 Thread Sean Bruno
bdrewery reported a vfs/zfs condition where operations will stall out and block (rm, mv, file) during a poudriere build. I've hit this now and it seems to be alleviated by setting vfs.lookup_shared=0 I seem to be able to trivially reproduce this on my builders and want to know if anyone is

Re: zfs/vfs lockups, via poudriere

2014-11-22 Thread Andriy Gapon
On 22/11/2014 21:20, Sean Bruno wrote: bdrewery reported a vfs/zfs condition where operations will stall out and block (rm, mv, file) during a poudriere build. I've hit this now and it seems to be alleviated by setting vfs.lookup_shared=0 I seem to be able to trivially reproduce this on my