From owner-freebsd-current@freebsd.org Mon Nov 23 21:12:28 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 75156A36C16 for ; Mon, 23 Nov 2015 21:12:28 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-yk0-x22a.google.com (mail-yk0-x22a.google.com [IPv6:2607:f8b0:4002:c07::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 393BF1F08 for ; Mon, 23 Nov 2015 21:12:28 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by ykba77 with SMTP id a77so252391935ykb.2 for ; Mon, 23 Nov 2015 13:12:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=06Lo2q22DOPIyB7sOtSnQwBA+4VO9WMW2XQLkT2nSOE=; b=ZyPfn4HmQs0Upzaguph7H1UZfQdVVbTAHrTRdDbocQdR1wXR4Yi9idHXeQg1ehTFQC 372oYjFslF2Ih9XmMM4lPmI99esAqS17GUNF5qy4Ix9fNVOsqIAKXxed/wG4MEwd3oXQ VbcXFIul7j/CiduIQrMiWPON3prlGlhzbFODTQBTldzK62lqHyqz7wcjgUxOCFY/DZ4W 35/6k0s9AbKD5pX/VUPi8LKo1farok2MgQPAPfkkJyvXxiuRac3L8aoYVQp/JOLcf7Fi wtQc7GvUcOm6Ryr0FjU23cvLQtHaKHP5Vs/TP/VwBGcJsnf9sAQfuUXD67BahJYfXt1t N7Mw== MIME-Version: 1.0 X-Received: by 10.129.44.11 with SMTP id s11mr24799463yws.74.1448313147409; Mon, 23 Nov 2015 13:12:27 -0800 (PST) Sender: markjdb@gmail.com Received: by 10.129.41.207 with HTTP; Mon, 23 Nov 2015 13:12:27 -0800 (PST) In-Reply-To: <5653798F.1060708@pix.net> References: <5653798F.1060708@pix.net> Date: Mon, 23 Nov 2015 13:12:27 -0800 X-Google-Sender-Auth: wB58f0b-dv4YLqPSFg6Om03wyso Message-ID: Subject: Re: New LOR in zfs? From: Mark Johnston To: Kurt Lidl Cc: FreeBSD-Current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Nov 2015 21:12:28 -0000 On Mon, Nov 23, 2015 at 12:39 PM, Kurt Lidl wrote: > I installed a build of r291086 on a machine today > (previously, the machine had been running 10/stable). > > I ran the following two commands just after rebooting > with the new user-land bits: > > root@ton-95: df > Filesystem 1K-blocks Used Avail Capacity Mounted on > sys/ROOT/default 18061924 804940 17256984 4% / > devfs 1 1 0 100% /dev > tmpfs 65536 8 65528 0% /tmp > sys/home 17257108 124 17256984 0% /home > sys/local 17283924 26940 17256984 0% /usr/local > sys/obj.4 19440624 2183640 17256984 11% /usr/obj > sys/obj.1 19440440 2183456 17256984 11% /usr/obj.1 > sys/obj.2 19588696 2331712 17256984 12% /usr/obj.2 > sys/obj.3 19588636 2331652 17256984 12% /usr/obj.3 > sys/ports 17257080 96 17256984 0% /usr/ports > sys/src 19740468 2483484 17256984 13% /usr/src > sys/var 17358024 101040 17256984 1% /var > root@ton-96: zfs set mountpoint=/usr/obj.4 sys/obj.4 > > I got a LOR (new to me, at any rate) on the console: > lock order reversal: > 1st 0xfffff8000612da38 zfs (zfs) @ /usr/src/sys/kern/vfs_mount.c:1224 > 2nd 0xfffff8000612d4b0 zfs_gfs (zfs_gfs) @ > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/gfs.c:494 > stack backtrace: > #0 0xc05b1e3c at __lockmgr_args???=?-~????+0xa3c > #1 0xc06a9118 at vop_std???=?-~????lock+0x38 > #2 0xc09e8164 at VOP_???=?-~????LOCK1_APV+0x104 > #3 0xc06d125c a???=?-~????t _vn_lock+0x9c > #4 0xc12a7b04 a???=?-~????t gfs_file_create+0x64 > #5 0xc12???=?-~????a7c14 at gfs_dir_create+0x14 > #6???=?-~???? 0xc139fc14 at zfsctl_mknode_sn???=?-~????apdir+0x54 > #7 0xc12a82bc at gfs???=?-~????_dir_lookup+0x31c > #8 0xc139f6cc???=?-~???? at zfsctl_root_lookup+0x12c > #9???=?-~???? 0xc139f7b4 at zfsctl_umount_sn???=?-~????apshots+0x54 > #10 0xc13bb44c at ???=?-~????zfs_umount+0x4c > #11 0xc06b34a8 ???=?-~????at dounmount+0xbc8 > #12 0xc06b38???=?-~????f0 at sys_unmount+0x410 > #13 0xc???=?-~????09de004 at syscall+0x3c4 > > The machine in question is a sparc4u machine, but I do not think > it matters. The garbled output should be fixed by r291217.