From owner-freebsd-current@freebsd.org Tue Nov 24 01:03:02 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 1A407A35802 for ; Tue, 24 Nov 2015 01:03:02 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (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 D00511ABD; Tue, 24 Nov 2015 01:03:01 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by obdgf3 with SMTP id gf3so1544769obd.3; Mon, 23 Nov 2015 17:03:01 -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=q9PLiJEser3pLyRURBhEQ5eU0/Of5G+EMFL1rULkIK8=; b=NZWvtWmfg2f+0iQ3lrpZ8kHizyhmM8Uq2WeQtqEW7f35l6pOYAwiPluTebIgzi0Rp2 l0a6xbubh31qAtGsM1Uhx1Qlq61rqZJ0OQglH/Cig83nC0J0HMVRmy2AOgUs4fnxfxlN DhFLVcmQfEs+20bhW8rWjNaWAYJmd3vyGJKjnk/FVWaoHrKTlZY7Fn+FABI5wki0Dz/w KfSDZoifooQGkH4K+Uwfl7dXDqiuGQKaZUbl6qKLc9cQj/so/sE8OIu8x3keRwTWA+jE K18VYD9SepTEMEA9/SAtri1nm2aDjOAugZwIlgstyx/WXcSJNTr1bFjaOn1eZwRXJjo0 souQ== MIME-Version: 1.0 X-Received: by 10.182.153.101 with SMTP id vf5mr18201401obb.81.1448326981165; Mon, 23 Nov 2015 17:03:01 -0800 (PST) Sender: asomers@gmail.com Received: by 10.202.0.7 with HTTP; Mon, 23 Nov 2015 17:03:01 -0800 (PST) In-Reply-To: References: <5653798F.1060708@pix.net> Date: Mon, 23 Nov 2015 18:03:01 -0700 X-Google-Sender-Auth: 7KV3nD2BhoG39VZ1i7Q3GD3WQos Message-ID: Subject: Re: New LOR in zfs? From: Alan Somers To: Mark Johnston Cc: Kurt Lidl , FreeBSD-Current , "will@freebsd.org" 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: Tue, 24 Nov 2015 01:03:02 -0000 On Mon, Nov 23, 2015 at 2:12 PM, Mark Johnston wrote: > 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. This is a tough one, but Will (CC'ed) has made some progress fixing it. -Alan