From owner-freebsd-fs@freebsd.org Sun May 28 16:25:49 2017 Return-Path: Delivered-To: freebsd-fs@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 8D37FD8528D for ; Sun, 28 May 2017 16:25:49 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 59F8414E3 for ; Sun, 28 May 2017 16:25:49 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 45A62421DF; Sun, 28 May 2017 18:25:37 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wQ0FmOC-prao; Sun, 28 May 2017 18:25:36 +0200 (CEST) Received: from [192.168.10.67] (opteron [192.168.10.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 96085421DE; Sun, 28 May 2017 18:25:36 +0200 (CEST) To: FreeBSD Filesystems Cc: Kees Meijs From: Willem Jan Withagen Subject: rbd-ggate released in Ceph master Message-ID: Date: Sun, 28 May 2017 18:25:34 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 May 2017 16:25:49 -0000 Hi, Just of those interested in cloud systems and reliability .... Mykola Golub mgolub@mirantis.com: --- rbd-ggate is a client for RADOS block device (rbd) images. It will map a rbd image to a ggate (FreeBSD GEOM Gate class) device, allowing access it as regular local block device. --- So it should now be possible to load a Rados block device and make it a disk under FreeBSD. And the Ceph cluster could very well be a Standard Linux cluster. --WjW From owner-freebsd-fs@freebsd.org Sun May 28 21:00:27 2017 Return-Path: Delivered-To: freebsd-fs@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 36091D86F2B for ; Sun, 28 May 2017 21:00:27 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2CE411886 for ; Sun, 28 May 2017 21:00:27 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4SL015J035962 for ; Sun, 28 May 2017 21:00:27 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201705282100.v4SL015J035962@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-fs@FreeBSD.org Subject: Problem reports for freebsd-fs@FreeBSD.org that need special attention Date: Sun, 28 May 2017 21:00:27 +0000 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 May 2017 21:00:27 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 203492 | mount_unionfs -o below causes panic New | 217062 | for file systems mounted with -o noexec, exec=off Open | 136470 | [nfs] Cannot mount / in read-only, over NFS Open | 139651 | [nfs] mount(8): read-only remount of NFS volume d Open | 140068 | [smbfs] [patch] smbfs does not allow semicolon in Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f Open | 211491 | System hangs after "Uptime" on reboot with ZFS 7 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Sun May 28 22:59:58 2017 Return-Path: Delivered-To: freebsd-fs@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 10A56D84868 for ; Sun, 28 May 2017 22:59:58 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [148.251.9.81]) by mx1.freebsd.org (Postfix) with ESMTP id 9383C1D53; Sun, 28 May 2017 22:59:57 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:e0f4:994:662:862]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id B59102B9; Mon, 29 May 2017 01:59:48 +0300 (MSK) Date: Mon, 29 May 2017 01:59:48 +0300 From: Lev Serebryakov Reply-To: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <1601598008.20170529015948@serebryakov.spb.ru> To: Andriy Gapon , freebsd-fs@FreeBSD.org Subject: Re: Strange behavior of .zfs/snapshot/* directories in respect to ".." path. In-Reply-To: References: <1acc5917-f10f-b18a-50e0-84661173e85d@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 May 2017 22:59:58 -0000 Hello Andriy, Friday, May 26, 2017, 8:34:31 PM, you wrote: > could you please test the following patch? (1) When I've updated to latest stable/11 revision (r319076) it crashed in ZFS(!) WITH AND WITHOUT patch soon after boot, 100% repeatable (looks like r318716 has HUGE problems): panic: solaris assert: pp != NULL && !pp->valid, file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c, line: 430 (kgdb) #0 doadump (textdump=1) at pcpu.h:222 #1 0xffffffff8056ce85 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:366 #2 0xffffffff8056d460 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:759 #3 0xffffffff8056d4a3 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:690 #4 0xffffffff812df23a in assfail (a=, f=, l=) at /usr/src/sys/cddl/compat/opensolaris/kern/opensolaris_cmn_err.c:81 #5 0xffffffff810478fc in zfs_freebsd_write (ap=) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:430 #6 0xffffffff80801518 in VOP_WRITE_APV (vop=, a=0xfffffe04760bd610) at vnode_if.c:1000 #7 0xffffffff80639eed in vn_write (fp=0xfffff80013cfb6e0, uio=0xfffffe04760bd8f0, active_cred=, flags=, td=) at vnode_if.h:413 #8 0xffffffff806379e0 in vn_io_fault1 () at /usr/src/sys/kern/vfs_vnops.c:1076 #9 0xffffffff80635fde in vn_io_fault (fp=, uio=, active_cred=, flags=1, td=) at /usr/src/sys/kern/vfs_vnops.c:1181 #10 0xffffffff805ca99a in dofilewrite (td=0xfffff8004d086000, fd=, fp=0xfffff80013cfb6e0, auio=0xfffffe04760bd8f0, offset=, flags=1) at file.h:307 #11 0xffffffff805ca7a0 in kern_pwritev (td=0xfffff8004d086000, fd=16, auio=0xfffffe04760bd8f0, offset=696) at /usr/src/sys/kern/sys_generic.c:556 #12 0xffffffff805ca67d in sys_pwrite (td=, uap=) at /usr/src/sys/kern/sys_generic.c:459 #13 0xffffffff8079f4c6 in amd64_syscall (td=0xfffff8004d086000, traced=0) at subr_syscall.c:135 #14 0xffffffff807827fb in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:396 #15 0x0000000804bb4bfa in ?? () (2) When I've reverted to r318576, this patch helps! > Thank you! > Index: sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c > =================================================================== > --- sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c (revision 318865) > +++ sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c (working copy) > @@ -1625,7 +1625,7 @@ zfs_lookup(vnode_t *dvp, char *nm, vnode_t **vpp, > cn.cn_nameptr = "snapshot"; > cn.cn_namelen = strlen(cn.cn_nameptr); > cn.cn_nameiop = cnp->cn_nameiop; > - cn.cn_flags = cnp->cn_flags; > + cn.cn_flags = cnp->cn_flags & ~ISDOTDOT; > cn.cn_lkflags = cnp->cn_lkflags; > error = VOP_LOOKUP(zfsctl_vp, vpp, &cn); > vput(zfsctl_vp); -- Best regards, Lev mailto:lev@FreeBSD.org From owner-freebsd-fs@freebsd.org Sun May 28 23:14:10 2017 Return-Path: Delivered-To: freebsd-fs@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 9A2D7D85028 for ; Sun, 28 May 2017 23:14:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 89CD41DB2 for ; Sun, 28 May 2017 23:14:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4SNEAYc052870 for ; Sun, 28 May 2017 23:14:10 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 219537] OpenZFS 8166 - zpool scrub thinks it repaired offline device Date: Sun, 28 May 2017 23:14:10 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 May 2017 23:14:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219537 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Mon May 29 06:11:24 2017 Return-Path: Delivered-To: freebsd-fs@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 BEDE7D86C21 for ; Mon, 29 May 2017 06:11:24 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B369C18C5; Mon, 29 May 2017 06:11:23 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id JAA14082; Mon, 29 May 2017 09:11:19 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1dFDtf-000MAB-Fy; Mon, 29 May 2017 09:11:19 +0300 Subject: Re: Strange behavior of .zfs/snapshot/* directories in respect to ".." path. To: Lev Serebryakov , freebsd-fs@FreeBSD.org References: <1acc5917-f10f-b18a-50e0-84661173e85d@FreeBSD.org> <1601598008.20170529015948@serebryakov.spb.ru> From: Andriy Gapon Message-ID: <8138588b-4b03-16d9-77b6-2a3e3444997d@FreeBSD.org> Date: Mon, 29 May 2017 09:09:58 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <1601598008.20170529015948@serebryakov.spb.ru> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 May 2017 06:11:24 -0000 On 29/05/2017 01:59, Lev Serebryakov wrote: > Hello Andriy, > > Friday, May 26, 2017, 8:34:31 PM, you wrote: > >> could you please test the following patch? > (1) When I've updated to latest stable/11 revision (r319076) it crashed in > ZFS(!) WITH AND WITHOUT patch soon after boot, 100% repeatable (looks like r318716 has HUGE problems): > > panic: solaris assert: pp != NULL && !pp->valid, file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c, line: 430 > > (kgdb) #0 doadump (textdump=1) at pcpu.h:222 > #1 0xffffffff8056ce85 in kern_reboot (howto=260) > at /usr/src/sys/kern/kern_shutdown.c:366 > #2 0xffffffff8056d460 in vpanic (fmt=, > ap=) at /usr/src/sys/kern/kern_shutdown.c:759 > #3 0xffffffff8056d4a3 in panic (fmt=) > at /usr/src/sys/kern/kern_shutdown.c:690 > #4 0xffffffff812df23a in assfail (a=, > f=, l=) > at /usr/src/sys/cddl/compat/opensolaris/kern/opensolaris_cmn_err.c:81 > #5 0xffffffff810478fc in zfs_freebsd_write (ap=) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:430 > #6 0xffffffff80801518 in VOP_WRITE_APV (vop=, > a=0xfffffe04760bd610) at vnode_if.c:1000 > #7 0xffffffff80639eed in vn_write (fp=0xfffff80013cfb6e0, > uio=0xfffffe04760bd8f0, active_cred=, > flags=, td=) at vnode_if.h:413 > #8 0xffffffff806379e0 in vn_io_fault1 () > at /usr/src/sys/kern/vfs_vnops.c:1076 > #9 0xffffffff80635fde in vn_io_fault (fp=, > uio=, active_cred=, flags=1, > td=) at /usr/src/sys/kern/vfs_vnops.c:1181 > #10 0xffffffff805ca99a in dofilewrite (td=0xfffff8004d086000, > fd=, fp=0xfffff80013cfb6e0, auio=0xfffffe04760bd8f0, > offset=, flags=1) at file.h:307 > #11 0xffffffff805ca7a0 in kern_pwritev (td=0xfffff8004d086000, fd=16, > auio=0xfffffe04760bd8f0, offset=696) > at /usr/src/sys/kern/sys_generic.c:556 > #12 0xffffffff805ca67d in sys_pwrite (td=, > uap=) at /usr/src/sys/kern/sys_generic.c:459 > #13 0xffffffff8079f4c6 in amd64_syscall (td=0xfffff8004d086000, traced=0) > at subr_syscall.c:135 > #14 0xffffffff807827fb in Xfast_syscall () > at /usr/src/sys/amd64/amd64/exception.S:396 > #15 0x0000000804bb4bfa in ?? () > > (2) When I've reverted to r318576, this patch helps! You probably meant r318716 again here? If yes, then it's probably exactly the same issue as we had in head: r308826. Could you please test if that change helps? I'll take care of this. >> Index: sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c >> =================================================================== >> --- sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c (revision 318865) >> +++ sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c (working copy) >> @@ -1625,7 +1625,7 @@ zfs_lookup(vnode_t *dvp, char *nm, vnode_t **vpp, >> cn.cn_nameptr = "snapshot"; >> cn.cn_namelen = strlen(cn.cn_nameptr); >> cn.cn_nameiop = cnp->cn_nameiop; >> - cn.cn_flags = cnp->cn_flags; >> + cn.cn_flags = cnp->cn_flags & ~ISDOTDOT; >> cn.cn_lkflags = cnp->cn_lkflags; >> error = VOP_LOOKUP(zfsctl_vp, vpp, &cn); >> vput(zfsctl_vp); > > > > -- Andriy Gapon From owner-freebsd-fs@freebsd.org Mon May 29 06:29:47 2017 Return-Path: Delivered-To: freebsd-fs@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 CA00ACA2E29 for ; Mon, 29 May 2017 06:29:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B908DCA8 for ; Mon, 29 May 2017 06:29:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4T6TkOS026527 for ; Mon, 29 May 2017 06:29:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 214629] [zfs] [panic] solaris assert: pp != NULL && !pp-valid, file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c, line: 430 Date: Mon, 29 May 2017 06:29:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 May 2017 06:29:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214629 --- Comment #6 from commit-hook@freebsd.org --- A commit references this bug: Author: avg Date: Mon May 29 06:15:07 UTC 2017 New revision: 319091 URL: https://svnweb.freebsd.org/changeset/base/319091 Log: MFC r308826: zfs: fix up after the removal of PG_CACHED pages in r308691 Now that r308691 has been MFC-ed as a part of r318716, r308826 must be MFC-ed as well. PR: 214629 Reported by: mshirk@daemon-security.com [head], lev [stable/11] Changes: _U stable/11/ stable/11/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon May 29 06:48:33 2017 Return-Path: Delivered-To: freebsd-fs@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 2B0D2CC2352 for ; Mon, 29 May 2017 06:48:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 14A41198C for ; Mon, 29 May 2017 06:48:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4T6mW8P091343 for ; Mon, 29 May 2017 06:48:32 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 219457] ZFS ARC eviction & system hangup Date: Mon, 29 May 2017 06:48:32 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 May 2017 06:48:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219457 Andriy Gapon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kib@FreeBSD.org, | |mjg@FreeBSD.org --- Comment #14 from Andriy Gapon --- Anton, I suspect that you could be running into a bug in fdalloc / fdgrowtable code that causes an attempt to allocate an insane amount of memory. The ARC is = just the first victim. Could you please try to use kgdb (preferably from devel/gdb) and check arguments and local variables in the relevant stack frames? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon May 29 10:20:18 2017 Return-Path: Delivered-To: freebsd-fs@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 16215CFACB2 for ; Mon, 29 May 2017 10:20:18 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [IPv6:2a01:4f8:201:6350::2]) by mx1.freebsd.org (Postfix) with ESMTP id D74BE73DF4; Mon, 29 May 2017 10:20:17 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:4478:eaa5:7c5a:516e]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id 3A3514D7; Mon, 29 May 2017 13:20:16 +0300 (MSK) Date: Mon, 29 May 2017 13:20:06 +0300 From: Lev Serebryakov Reply-To: lev@FreeBSD.org Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <1279842496.20170529132006@serebryakov.spb.ru> To: Andriy Gapon , freebsd-fs@FreeBSD.org Subject: Re: Strange behavior of .zfs/snapshot/* directories in respect to ".." path. In-Reply-To: <8138588b-4b03-16d9-77b6-2a3e3444997d@FreeBSD.org> References: <1acc5917-f10f-b18a-50e0-84661173e85d@FreeBSD.org> <1601598008.20170529015948@serebryakov.spb.ru> <8138588b-4b03-16d9-77b6-2a3e3444997d@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1250 Content-Transfer-Encoding: base64 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 May 2017 10:20:18 -0000 SGVsbG8gQW5kcml5LA0KDQpNb25kYXksIE1heSAyOSwgMjAxNywgOTowOTo1OCBBTSwgeW91 IHdyb3RlOg0KDQo+PiAgKDIpIFdoZW4gSSd2ZSByZXZlcnRlZCB0byByMzE4NTc2LCB0aGlz IHBhdGNoIGhlbHBzIQ0KPiBZb3UgcHJvYmFibHkgbWVhbnQgcjMxODcxNiBhZ2FpbiBoZXJl Pw0KIE5vcGUuIHIzMTg1NzYuIEkndmUgZm91bmQgInNuYXBzaG90IC4uIiBidWcgYXQgcjMx ODU3NiAoc2VlIG15IGZpcnN0IG1lc3NhZ2UpLA0Kc28gd2hlbiAibGF0ZXN0IiAoSSdtIHVz aW5nIGxvY2FsIG1pcnJvciwgc28gaXQgY291bGQgYmUNCm5vdC1yZWFsbHktbGF0ZXN0LW9u ZSkgcmV2aXNpb24glyByMzE5MDc2IJcgY3Jhc2hlZCwgSSd2ZSByZXZlcnRlZCB0bw0KZXhh Y3RseSB0aGlzICJwcm92ZW4iIHJldmlzaW9uIJcgcjMxODU3Ni4gUGF0Y2ggZm9yICJzbmFw c2hvdCAuLiIgd2FzIHRlc3RlZA0KYXQgcjMxODU3NiwgYW5kIGNyYXNoIHdpdGggYW5kIHdp dGhvdXQgcGF0Y2ggZm9yICJzbmFwc2hvdCIgd2FzIGF0IHIzMTkwNzYuDQoNCj4gSWYgeWVz LCB0aGVuIGl0J3MgcHJvYmFibHkgZXhhY3RseSB0aGUgc2FtZSBpc3N1ZSBhcyB3ZSBoYWQg aW4gaGVhZDogcjMwODgyNi4NCj4gQ291bGQgeW91IHBsZWFzZSB0ZXN0IGlmIHRoYXQgY2hh bmdlIGhlbHBzPw0KPiBJJ2xsIHRha2UgY2FyZSBvZiB0aGlzLg0KIE5vdywgYXMgcjMxOTA5 MSB3YXMgY29tbWl0dGVkLCBJJ20gYnVpbGRpbmcgbmV3IGZyZXNoIGtlcm5lbC4NCg0KDQot LSANCkJlc3QgcmVnYXJkcywNCiBMZXYgICAgICAgICAgICAgICAgICAgICAgICAgICAgbWFp bHRvOmxldkBGcmVlQlNELm9yZw== From owner-freebsd-fs@freebsd.org Mon May 29 10:23:30 2017 Return-Path: Delivered-To: freebsd-fs@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 82D7DCFAEA1 for ; Mon, 29 May 2017 10:23:30 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A3701740DA; Mon, 29 May 2017 10:23:29 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA14688; Mon, 29 May 2017 13:23:21 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1dFHpZ-000MNg-Cy; Mon, 29 May 2017 13:23:21 +0300 Subject: Re: Strange behavior of .zfs/snapshot/* directories in respect to ".." path. To: lev@FreeBSD.org, freebsd-fs@FreeBSD.org References: <1acc5917-f10f-b18a-50e0-84661173e85d@FreeBSD.org> <1601598008.20170529015948@serebryakov.spb.ru> <8138588b-4b03-16d9-77b6-2a3e3444997d@FreeBSD.org> <1279842496.20170529132006@serebryakov.spb.ru> From: Andriy Gapon Message-ID: <01c59f49-f45a-b02f-31f1-88c130609094@FreeBSD.org> Date: Mon, 29 May 2017 13:22:25 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <1279842496.20170529132006@serebryakov.spb.ru> Content-Type: text/plain; charset=windows-1250 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 May 2017 10:23:30 -0000 On 29/05/2017 13:20, Lev Serebryakov wrote: > Hello Andriy, > > Monday, May 29, 2017, 9:09:58 AM, you wrote: > >>> (2) When I've reverted to r318576, this patch helps! >> You probably meant r318716 again here? > Nope. r318576. Sorry, it was my confusion, I read "reverted to r318576" as "reverted r318576". > I've found "snapshot .." bug at r318576 (see my first message), > so when "latest" (I'm using local mirror, so it could be > not-really-latest-one) revision r319076 crashed, I've reverted to > exactly this "proven" revision r318576. Patch for "snapshot .." was tested > at r318576, and crash with and without patch for "snapshot" was at r319076. > >> If yes, then it's probably exactly the same issue as we had in head: r308826. >> Could you please test if that change helps? >> I'll take care of this. > Now, as r319091 was committed, I'm building new fresh kernel. Thank you. Please let me know how it goes. -- Andriy Gapon From owner-freebsd-fs@freebsd.org Mon May 29 12:43:36 2017 Return-Path: Delivered-To: freebsd-fs@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 F369CCFE31B for ; Mon, 29 May 2017 12:43:36 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [IPv6:2a01:4f8:201:6350::2]) by mx1.freebsd.org (Postfix) with ESMTP id B3A8077F4C; Mon, 29 May 2017 12:43:36 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.17.133] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id 6E746540; Mon, 29 May 2017 15:43:35 +0300 (MSK) Reply-To: lev@FreeBSD.org Subject: Re: Strange behavior of .zfs/snapshot/* directories in respect to ".." path. To: Andriy Gapon , freebsd-fs@FreeBSD.org References: <1acc5917-f10f-b18a-50e0-84661173e85d@FreeBSD.org> <1601598008.20170529015948@serebryakov.spb.ru> <8138588b-4b03-16d9-77b6-2a3e3444997d@FreeBSD.org> <1279842496.20170529132006@serebryakov.spb.ru> <01c59f49-f45a-b02f-31f1-88c130609094@FreeBSD.org> From: Lev Serebryakov Organization: FreeBSD Message-ID: <5d9dbe2e-9d51-0df2-1280-25ccbe710900@FreeBSD.org> Date: Mon, 29 May 2017 15:43:27 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <01c59f49-f45a-b02f-31f1-88c130609094@FreeBSD.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="J358pxmpA5C9V0EAH9crIi78Bif6Tp1RJ" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 May 2017 12:43:37 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --J358pxmpA5C9V0EAH9crIi78Bif6Tp1RJ Content-Type: multipart/mixed; boundary="V9mjt5MmPqhkrHXESex2Wthd0NO7xspQe"; protected-headers="v1" From: Lev Serebryakov Reply-To: lev@FreeBSD.org To: Andriy Gapon , freebsd-fs@FreeBSD.org Message-ID: <5d9dbe2e-9d51-0df2-1280-25ccbe710900@FreeBSD.org> Subject: Re: Strange behavior of .zfs/snapshot/* directories in respect to ".." path. References: <1acc5917-f10f-b18a-50e0-84661173e85d@FreeBSD.org> <1601598008.20170529015948@serebryakov.spb.ru> <8138588b-4b03-16d9-77b6-2a3e3444997d@FreeBSD.org> <1279842496.20170529132006@serebryakov.spb.ru> <01c59f49-f45a-b02f-31f1-88c130609094@FreeBSD.org> In-Reply-To: <01c59f49-f45a-b02f-31f1-88c130609094@FreeBSD.org> --V9mjt5MmPqhkrHXESex2Wthd0NO7xspQe Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 29.05.2017 13:22, Andriy Gapon wrote: >> Now, as r319091 was committed, I'm building new fresh kernel. > Thank you. Please let me know how it goes. I don't have any problems with r319091 + patch for "..". --=20 // Lev Serebryakov --V9mjt5MmPqhkrHXESex2Wthd0NO7xspQe-- --J358pxmpA5C9V0EAH9crIi78Bif6Tp1RJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJZLBdvXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePk1EP/3gyOJKcObfq1S0MiUBMaViM FXL1eOrtNVl7kCFnpRmsNDn74b8QtbC36z9MqDP7ZXrxLzXurPJxtG9bq4T/A4rp ts/YQZUL1Qs2fxuX7VUXIOkLHSfpufsr72CqyPk5XEkyNzPiJqRUEKMJUuUbidDv V1c62eJLjf/gY2Dli0mNZCZSqgxmauip2FvVcwloLSiwsM4FG/RubmamZDRvaKbB 22aYdHA8APhni4DpEddwVCu/vLVzb2kIh0pd/MzVdoLHchVOiegtmJUw4jpwxPyI O9W6Yboskh36dssP5AQu4p0nrH1ZVVHB/GPtgHXqIrd/VsC9siL76wuVWwmKez5e 7BHrBvEV+ryfsf+bc1uD1MEMPVq18RSDF8C4OSyXrxh9caiGIcBV/6VPiWKanM3U v/rYnOI2UcJ1gagQksjkxy0D0X1G8wXC8u/mG2wJtxAqmO/H6TFDCdM2ma8XXAgC nPHzRGujLKoqvD5/vJ8EDBuJ9zPcd5SzxUPQMafbMf+Q+GAbDUL0GsswaDsISzcR 34w9QAqXp6rofxt/EFRIAa2clUD44rf9WchpVOepaFE43FPDavkzQXmSg6jOofRv AsrL5R9Yuu7Dkjr+plPXYTnK8MvoeIKZYgKniUTIWTXqd6ZVOEktpuwHHXBwYy3z qzzjPPbiKaJZhXtNpJIm =eMDb -----END PGP SIGNATURE----- --J358pxmpA5C9V0EAH9crIi78Bif6Tp1RJ-- From owner-freebsd-fs@freebsd.org Mon May 29 12:46:31 2017 Return-Path: Delivered-To: freebsd-fs@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 B667ACFE38D for ; Mon, 29 May 2017 12:46:31 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id D050377FF9; Mon, 29 May 2017 12:46:30 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA15009; Mon, 29 May 2017 15:46:28 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1dFK44-000MUW-Mh; Mon, 29 May 2017 15:46:28 +0300 Subject: Re: Strange behavior of .zfs/snapshot/* directories in respect to ".." path. To: lev@FreeBSD.org, freebsd-fs@FreeBSD.org References: <1acc5917-f10f-b18a-50e0-84661173e85d@FreeBSD.org> <1601598008.20170529015948@serebryakov.spb.ru> <8138588b-4b03-16d9-77b6-2a3e3444997d@FreeBSD.org> <1279842496.20170529132006@serebryakov.spb.ru> <01c59f49-f45a-b02f-31f1-88c130609094@FreeBSD.org> <5d9dbe2e-9d51-0df2-1280-25ccbe710900@FreeBSD.org> From: Andriy Gapon Message-ID: Date: Mon, 29 May 2017 15:45:33 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <5d9dbe2e-9d51-0df2-1280-25ccbe710900@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 May 2017 12:46:31 -0000 On 29/05/2017 15:43, Lev Serebryakov wrote: > On 29.05.2017 13:22, Andriy Gapon wrote: > >>> Now, as r319091 was committed, I'm building new fresh kernel. >> Thank you. Please let me know how it goes. > I don't have any problems with r319091 + patch for "..". > Thank you for testing! -- Andriy Gapon From owner-freebsd-fs@freebsd.org Tue May 30 02:52:02 2017 Return-Path: Delivered-To: freebsd-fs@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 2B6FFAF7EBD for ; Tue, 30 May 2017 02:52:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1986672783 for ; Tue, 30 May 2017 02:52:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4U2q1Hq039596 for ; Tue, 30 May 2017 02:52:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 219646] "ls: fts_read: no such file or directory" in zfs snapshot dir Date: Tue, 30 May 2017 02:52:02 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: g_amanakis@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 02:52:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219646 g_amanakis@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Tue May 30 05:32:59 2017 Return-Path: Delivered-To: freebsd-fs@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 E059AAFD0DD for ; Tue, 30 May 2017 05:32:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CEFEA79123 for ; Tue, 30 May 2017 05:32:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4U5WxEp065035 for ; Tue, 30 May 2017 05:32:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 219646] "ls: fts_read: no such file or directory" in zfs snapshot dir Date: Tue, 30 May 2017 05:32:59 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 05:33:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219646 --- Comment #1 from Andriy Gapon --- Please see if r319096 helps with that issue. I am going to MFC that change soon. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Tue May 30 13:17:14 2017 Return-Path: Delivered-To: freebsd-fs@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 0D4ABB7CAE9 for ; Tue, 30 May 2017 13:17:14 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 70357A8C for ; Tue, 30 May 2017 13:17:13 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from moby.local ([78.55.171.71]) by mail.gmx.com (mrgmx101 [212.227.17.174]) with ESMTPSA (Nemesis) id 0LbyUS-1df69a1KI0-00jHVx; Tue, 30 May 2017 15:17:10 +0200 Subject: Re: rbd-ggate released in Ceph master To: Willem Jan Withagen , FreeBSD Filesystems Cc: Kees Meijs References: From: Nikos Vassiliadis Message-ID: <3c0dd6f6-141d-bb40-cb93-72275ffa9d71@gmx.com> Date: Tue, 30 May 2017 15:17:03 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:8VMI/vNmHRGal/L0Gw5uDkArLBlLmdiCW0V7c2f4lmN4y83uE+S dbjrfbv4vBrCauH2GwwDrAiNrhCowMN4JFNRGlV3qbj3TUypgx8WKCklBKTjWoCZrc1XBKk BZA3i5UJp5WkBy4GBJB5rF9lMq6B7gAxBddRtB/Mf7lkwHkdb/a0KzWWBmlp5hlHrUKdfOa o2xHUYIQI9si2zGwVMUeQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:30eO5H/E1Cc=:iiFpkC6KSN+ZRdcncklyLE 1PKseta1Du6lY0aXcMwFt/G9kLeTGcxqi7gHmCa8lR5Y/0FH3yMdU0lm2qb9+xY/qb8Qu89n8 NCpD0KGRHUrp82BGaeflwHe82DHZNCtLcroHKDUi39F15Qba/1f7IVI0xS2fPF7UdHlvCVxr8 4NgTr1ABep5P/0xsOvF624oRJF69UU8LQS8bxspwsOIZ37za1ECNmzyjiWo8ON2VbE8P+A/C5 r4KC2PtkvvaY/goc4X3Y32G+G7mle+fCzbkztWcXS+0yBZgLoTZlRYZTMQXlqKOD2hfvs7Y4Q grJx/VoX6X+NSg5omu+sdSvMplQzvzKqAI6ZNviDb6gaJPba59drVf35xBaVGsi4GfX8VR6A+ HRjYLMvlWJ3nLELNZ3HQzQyP+NTR2kVZmL6W0taSKkg8avaRDcwrU5QvEaNOqt+9A/Qkkl0sq t1IgUlXdoKCnJ++45xFUVYmlLwLhH6VsK5Xp0CypaHh8IK1H7apd3tWP6RNy/obtFg8svuNJX IQFWVqPPu6g0yqLP0ex+AqmZ5Ti+q99Ocn1OKURf6tjkkPcZVThmJOUbB5O/9bbRe+eDev0Yk pP1Sf2vhzgDsAXO/WJvjwjFl4bi03cRHn0NEB4cZdRjihFH7XONDTatlUQ0zl/rLbEXpyVOn4 208lkEg5kYpgI7rZrkaSt01h+XNmPu2TGKRkbPttdFcJyOl3ux2DauYHJ63haQgBoMnWkJRQ3 gmRjI2HWSML8L5slS9G34YCcu/27nbrsV0vdrH5wRDfUMc1GtxLB0ZND3WDdeaSjzB9HhnxrA QFX7PQg X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 13:17:14 -0000 Hi Willem, glad to see that your efforts wrt ceph:) Where could one get this rbd-ggate module? Best, Nikos On 05/28/17 18:25, Willem Jan Withagen wrote: > Hi, > > Just of those interested in cloud systems and reliability .... > > Mykola Golub mgolub@mirantis.com: > --- > rbd-ggate is a client for RADOS block device (rbd) images. It will > map a rbd image to a ggate (FreeBSD GEOM Gate class) device, allowing > access it as regular local block device. > --- > > So it should now be possible to load a Rados block device and make it a > disk under FreeBSD. And the Ceph cluster could very well be a Standard > Linux cluster. > > --WjW > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@freebsd.org Tue May 30 13:28:35 2017 Return-Path: Delivered-To: freebsd-fs@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 04113B7CF09 for ; Tue, 30 May 2017 13:28:35 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C33E415A5 for ; Tue, 30 May 2017 13:28:34 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 2EC1042B23; Tue, 30 May 2017 15:28:31 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LId8YQ8HHlYI; Tue, 30 May 2017 15:28:30 +0200 (CEST) Received: from [192.168.10.67] (opteron [192.168.10.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 5145F42B22; Tue, 30 May 2017 15:28:30 +0200 (CEST) Subject: Re: rbd-ggate released in Ceph master To: Nikos Vassiliadis , FreeBSD Filesystems References: <3c0dd6f6-141d-bb40-cb93-72275ffa9d71@gmx.com> From: Willem Jan Withagen Message-ID: <2ba3e8f4-4b35-52c7-8c8a-459ebfff29f1@digiware.nl> Date: Tue, 30 May 2017 15:28:24 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <3c0dd6f6-141d-bb40-cb93-72275ffa9d71@gmx.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 13:28:35 -0000 On 30-5-2017 15:17, Nikos Vassiliadis wrote: > Hi Willem, > > glad to see that your efforts wrt ceph:) > Where could one get this rbd-ggate module? Hi Nikos, At the moment that is only possible by building from source from my private git-repo. The current dev-package got snapshotted beginning of May, which was before the release of rbd-ggate. I'll probably make another snapshot beginning of july, and that'll include the module (and all the other ceph-stuff) And note that I've not yet tested it in any serious way, other than that it loads. --WjW > > Best, > Nikos > > On 05/28/17 18:25, Willem Jan Withagen wrote: >> Hi, >> >> Just of those interested in cloud systems and reliability .... >> >> Mykola Golub mgolub@mirantis.com: >> --- >> rbd-ggate is a client for RADOS block device (rbd) images. It will >> map a rbd image to a ggate (FreeBSD GEOM Gate class) device, allowing >> access it as regular local block device. >> --- >> >> So it should now be possible to load a Rados block device and make it a >> disk under FreeBSD. And the Ceph cluster could very well be a Standard >> Linux cluster. >> >> --WjW >> >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >> From owner-freebsd-fs@freebsd.org Tue May 30 13:57:40 2017 Return-Path: Delivered-To: freebsd-fs@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 2F5F8B7D98B for ; Tue, 30 May 2017 13:57:40 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8B4212F67 for ; Tue, 30 May 2017 13:57:39 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from moby.local ([78.55.171.71]) by mail.gmx.com (mrgmx103 [212.227.17.174]) with ESMTPSA (Nemesis) id 0MIuft-1dDDk20icb-002UNH; Tue, 30 May 2017 15:57:31 +0200 Subject: Re: rbd-ggate released in Ceph master To: Willem Jan Withagen , FreeBSD Filesystems References: <3c0dd6f6-141d-bb40-cb93-72275ffa9d71@gmx.com> <2ba3e8f4-4b35-52c7-8c8a-459ebfff29f1@digiware.nl> From: Nikos Vassiliadis Message-ID: Date: Tue, 30 May 2017 15:57:30 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: <2ba3e8f4-4b35-52c7-8c8a-459ebfff29f1@digiware.nl> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:uhg3YraczTbD9FzBzGo+hyHpsEBTfqc1h7Vip3/PVxTppCDJIfJ 0uT+4j4DNGaxLDi2/XffbMhvh1RTk73H/J/ABwS2rAkQnDVMZWjuxragIUslC8U9LfuIPya DmvK97Wp91UsfkoRbM8TkGFigPJmq0zkerm0tC77Aof85RY4IJMxc/TJVDdFXJl4vh3nPQ+ C9ifipmdAPZXc8fsp2ccg== X-UI-Out-Filterresults: notjunk:1;V01:K0:RFXCKBIEEz0=:0udPvsq+2sU78pbf87l8NL I7YDvVDbHpMXZcNokNaRGIpuaS5q4MR/KOiWBEZe4y6uLyByCQ9QWISNVGiYJTKt/ZIt2AovU N1ZzONdPx8jZAS9mDySJU/YDn1cjIWARneEFO69WAIukEB/kYFWmJBchUaXGuNdWok1vX8lz6 dj8GFyQlLnepeNYKoJnJKwMK/RRcDFRNSFiHLCl4mITDbPz6VMaJS5EhRy5wAEotLuWWDTRTr cRT3K/D5wAt1Bblf6gZzFWEnMeTcVATlfbzRL6fERY7CtAHZeX81hJxNvJWqlSzL9wDOMVhq7 rmdlrZ0ihoeah8iYo21kohyqfXGgvCMultvQb5hsa7jsSISkt0uJfQ6QO/k2HvsFvysoSRGcY zGosSffHmAzNIdb0qRtlhcP25d2hwq4Z/l1JeOLcX9SlibVu8FigHnnA5LkGJHGoKSK7MB68/ iOpB4qaDN+820B7zaXmpTqk3AJiOg6Oy7uP1jVRm46JFYjxnv5SNjx8nflGFsQ0ForWl8xZqF lwRA9F+EvTkiBQbdSUw5Tn43j1PrqKr+ZiqyiYOFhJdYUPiQa2kDvQEw1p2evLvKyrYo5ENFE 7UnSATsMxKSSK/kjbVGI0nvdx6MzXlsZG0KQsOByx/OeJNhp5T2vnGq/49jUj0DWUyUmejepk KNpnqPJp/SLi8qRnkFh8viLMMnAEZCaSlbfW59zxbBk0TXPl1T1vNGXAkyPEvgpLYgHClll78 tDI+Ea3aQEQegz0z/CZznfXAMUPVXyX2Oe6ufutsEQROY32RcVGwz0bSuP59mfvU0m5xa5yaG sA02GCh X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 13:57:40 -0000 On 05/30/17 15:28, Willem Jan Withagen wrote: > At the moment that is only possible by building from source from my > private git-repo. > > The current dev-package got snapshotted beginning of May, which was > before the release of rbd-ggate. > I'll probably make another snapshot beginning of july, and that'll > include the module (and all the other ceph-stuff) > > And note that I've not yet tested it in any serious way, other than that > it loads. > > --WjW Sounds great. Looking forward to it. Nikos From owner-freebsd-fs@freebsd.org Tue May 30 15:04:34 2017 Return-Path: Delivered-To: freebsd-fs@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 203AEB7EEB5 for ; Tue, 30 May 2017 15:04:34 +0000 (UTC) (envelope-from alex@nixd.org) Received: from mail.nixd.org (mail.nixd.org [95.211.160.151]) by mx1.freebsd.org (Postfix) with ESMTP id C3048656B6 for ; Tue, 30 May 2017 15:04:33 +0000 (UTC) (envelope-from alex@nixd.org) Received: from spamfilter (spamfilter.jail.localhost [192.168.1.4]) by mail.nixd.org (Postfix) with ESMTP id 28AAA2E8E for ; Tue, 30 May 2017 16:43:03 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nixd.org; h= user-agent:message-id:organization:subject:subject:from:from :date:date:content-transfer-encoding:content-type:content-type :mime-version:received:received; s=default; t=1496155376; bh=pdf CwuRw2vmM/THh2kBFNQYVHdCRgeWkbeUuXqaLv1A=; b=fU6Mqkfg5nfY+X2NDhB RJKNRmtETyevoNv8mkCep/Af3Olo/s3ccnna9dfhGLjYvDxORjr+T2BTZEGEVPul 1P1/3jlF0eLSchuNoP9VCzUwg/x8yF/IERsDlH13dELvoO5fY2dLkC5TSn4oQ77H NDpKLRhLG5MI2QXASK7u1E4A= X-Virus-Scanned: amavisd-new at nixd.org Received: from mail.nixd.org ([192.168.1.2]) by spamfilter (nixd.org [192.168.1.4]) (amavisd-new, port 10024) with ESMTP id iBS3dTMSJ5nn for ; Tue, 30 May 2017 16:42:56 +0200 (CEST) Received: from nixd.org (webserver.jail.localhost [192.168.1.1]) by mail.nixd.org (Postfix) with ESMTPA id A70892E8D for ; Tue, 30 May 2017 16:42:56 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 30 May 2017 19:42:56 +0500 From: Alexander Morozov To: freebsd-fs@freebsd.org Subject: VFS vn_lock function makes system unresponsive when calling vn_fullpath Organization: NiXD Message-ID: <38666c423c33a5e1009c106c23aeb218@nixd.org> X-Sender: alex@nixd.org User-Agent: Roundcube Webmail/1.2.5 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 15:04:34 -0000 Hi, At the moment I am developing a kernel module based on MAC Framework which is invoking a vn_fullpath() from vfs_cache.c. Here is the thing: When the MAC Framework mpo_vnode_check_write procedure is called, the kernel module is trying to retrieve: the path on the disk for the curthread and the path of the file in which the curthread is attempting to write. At the point when the program execution reaches the vn_fullpath() for the resolution of the file's path, the terminal window 'freezes' (actually the whole system is not responding, the rest ttys stop responding after entering login credentials). For instance, after loading and initializing a MAC kernel module, I am opening a existing text file using vi to edit it. After inserting some random text I press ESC key on keyboard and terminal window 'freezes' (at that moment the mpo_vnode_check_write is called) ( the struct vnode * vp which is passed to the MAC procedure is valid (not NULL) and type (enum vtype) is VREG). I have investigated this issue and found out the following: The get_fullpath() is calling the get_fullpath1() where later the vn_vptocnp() is invoked. Retrieving the location for the curthread is successful (the full path returned). But when the kernel module is making attempt to retrieve the path for the vp (argument of the mpo_vnode_check_write) the function vn_lock(*vp, LK_SHARED | LK_RETRY) (line 2191) located in function vn_vptocnp() is grabbing control forever. Running the kernel in debug mode showed that (in the case with vi described above) the condition check if (ncp != NULL) (line 2167) fails, the ncp is NULL. In such case the program exec goes further, continuing from SDT_PROBE1(vfs, namecache, fullpath, miss, vp); (line 2188). When vn_lock (line 2191) is entered, it can't return from vn_lock for some reason. Referring to the DDB tracing, the code can't lock vp (vnode) and as a result loop this operation. It seems that LK_RETRY does not allow to return from function without locking vnode instance otherwise it would simply return error code. The trace: VOP_LOCK1__APV() _vn_lock() _vn_vptocnp_locked() (Sometimes the DDB stops breaking execution after requesting 's' single step and I can't investigate the problem any further, need to restart the VM. This time it stoped at VOP_LOCK_APV+0x11: testq %rdi, %rdi) I am trying to figure out why the system can't lock it. It seems that the file either does not exist, so there is nothing to lock or some exclusive lock was applied (I will check it later). Any ideas or comments on this problem are welcomed! The same problem when I am closing the the mc-light (midnight commander). The OS is running as the guest in the VrtualBox (single core, 1024MB RAM). uname -a FreeBSD 11.0-RELEASE-p10 FreeBSD 11.0-RELEASE-p10 #0 r318316M: Tue May 30 07:41:36 UTC 2017 root@:/usr/obj/usr/src/sys/MYKERN amd64 The kernel was rebuild with additional option (options DDB). Below I have copied and pasted the code which performers the path resolution and the MAC procedure handler: static int rw_retreive_data(struct thread * td, struct vnode *dvp, char ** rpath, char ** curpath, struct sandbox_rule_app ** rule_ptr) { ASSERT_NULL_R(dvp, -1); ASSERT_NULL_R(rpath, -1); ASSERT_NULL_R(curpath, -1); ASSERT_NULL_R(rule_ptr, -1); char * fpath = NULL; char * curfreepath = NULL; int error = 0; error = vn_fullpath(td, td->td_proc->p_textvp, curpath, &curfreepath); if (error != 0) { printf("sandbox: %s error! vn_fullback returned [%d]\r\n", __FUNCTION__, error); return -1; } uprintf("1: %s path: %s\r\n", __FUNCTION__, *curpath); uprintf("2: %s path: vtype %d v_iflag %u v_vflag %u\r\n", __FUNCTION__, dvp->v_type, dvp->v_iflag, dvp->v_vflag); error = vn_fullpath(td, dvp, rpath, &fpath); if (error != 0) { //handle errorno there before returning printf("sandbox: %s error! vn_fullback returned [%d]\r\n", __FUNCTION__, error); error = ENOENT; goto leave; } //uprintf("2: %s path: %s vtype %d v_iflag %u v_vflag %u\r\n", __FUNCTION__, *rpath, dvp->v_type, dvp->v_iflag, dvp->v_vflag); if (rules_lookup_app_rule_bypath(*curpath, rule_ptr) != 0) { //not found, return -1 because the exec path was found, but the operated file can not be found (cache purged???) printf("sandbox: %s Rule was not found in rule list for [%s].\r\n", __FUNCTION__, *curpath); error = -1; } leave: if (fpath != NULL) { KFREE((void*) fpath); } if (curfreepath != NULL) { KFREE((void*) curfreepath); } return error; } int sandbox_vnode_check_write(struct ucred *active_cred, struct ucred *file_cred, struct vnode *vp, struct label *vplabel) { IS_MODULE_INITED(0) ASSERT_NULL_R(vp, 0); struct sandbox_rule_app * rule_ptr = NULL; char * rpath = "-"; char * curpath = "-"; int error = 0; RWLOCK_BLOCK(&sandbox_rules_lock, RWLOCK_READ) { error = rw_retreive_data(curthread, vp, &rpath, &curpath, &rule_ptr); if (error == 0) { //printf("--> sandbox: debug, writing to %s\r\n", rpath); error = sandboxing_check_filewritedata(rule_ptr, rpath); } else { printf("debug_write %s %s\r\n", rpath, curpath); error = get_rule_notfound_policy(error); } } //RWLOCK_BLOCK return (error); } -- Kind Regards, Alexander Morozov From owner-freebsd-fs@freebsd.org Tue May 30 16:47:28 2017 Return-Path: Delivered-To: freebsd-fs@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 7DA67B87D0A for ; Tue, 30 May 2017 16:47:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6C55B6EF73 for ; Tue, 30 May 2017 16:47:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4UGlRpm069853 for ; Tue, 30 May 2017 16:47:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 219457] ZFS ARC eviction & system hangup Date: Tue, 30 May 2017 16:47:27 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: vsasjason@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 16:47:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219457 --- Comment #15 from Anton Sayetsky --- (In reply to Andriy Gapon from comment #14) Running devel/gdb is possible but I need some instructions because I have almost no experience with it. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue May 30 19:27:23 2017 Return-Path: Delivered-To: freebsd-fs@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 A2E0DBDA1A4 for ; Tue, 30 May 2017 19:27:23 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::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 6AF6B760E8 for ; Tue, 30 May 2017 19:27:23 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-qk0-x22a.google.com with SMTP id u75so76836031qka.3 for ; Tue, 30 May 2017 12:27:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=x//YYnRc5vdJuwcrSORs41aNoZrcjW7meLGG37s9304=; b=CXsEfLereuw/eKdkhKGP68GsAWSBwzlGBPzU2LcjW2Og8D1qy//idbb9bo3NPXPtch 2rnhAQTMMIMX0AIqiNZ9QZtfSVxK2s/GLpz/qH3bfTec/h9yc5euXb/Bl7ZSNRh1QkYr hBL242P6DoJ0EkKYkY8oa1PAe4CV5hXc8xzAPYrODXJV4kKQLfGrEvMrxGVMhkjNeX/O gd7EVbzR5YHBWiLwPXhIQQYroSA4RwuovhPBPKknHMpIwEzooX2HECpHd4fDqNiN0BaB zAFOEo9GDBrtEGal7tgjJwePGMApOD7oxFOhJUxtK4kK8jd2PhZGtfwbNotAl6sJO5BP yoJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=x//YYnRc5vdJuwcrSORs41aNoZrcjW7meLGG37s9304=; b=Jmu7cA5rx3fDrAwGbKMG0u6p2N9XIGbGMFlBBIlHr1le0+U1wBblCOOFCR97QqS3zV 5+d84ZQ1e3hOoUKEYdiUuLosjeB6ITnyWJOQ4MraGkskbcYtkUUEHpIfjvUfP3J6BH1u acPTZRiIYxxbq5NfK++8bcDOf1gKyz6Mqvet7hGR042evvTYeZg1b3J7j6GTcvZYaqBF Irgq7GUcN7G9Dj1eSbTH7IrO2l1Px8NPU9XEecOFLE4i8sNh4uzSVTPz6tfyckKo4hcE Je2oLbmN7t3PmqG8WBdShBEgl5xk55r6JFeXKsByUFyNEn3hdI705d3KlTJ0jxGm7csm stAA== X-Gm-Message-State: AODbwcAN7bIOqcCm7sS2ZZm9ZGRx4WEqoTFdkgwg0tMQtX9I7kwFCHoO LCPW8cd7oQcJ08hpO6kus9ZNluRrag== X-Received: by 10.55.217.70 with SMTP id u67mr24621311qki.17.1496172442521; Tue, 30 May 2017 12:27:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.61.154 with HTTP; Tue, 30 May 2017 12:27:22 -0700 (PDT) In-Reply-To: <38666c423c33a5e1009c106c23aeb218@nixd.org> References: <38666c423c33a5e1009c106c23aeb218@nixd.org> From: Mateusz Guzik Date: Tue, 30 May 2017 21:27:22 +0200 Message-ID: Subject: Re: VFS vn_lock function makes system unresponsive when calling vn_fullpath To: Alexander Morozov Cc: "freebsd-fs@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 19:27:23 -0000 On Tue, May 30, 2017 at 4:42 PM, Alexander Morozov wrote: > Hi, > > At the moment I am developing a kernel module based on MAC Framework which > is invoking a vn_fullpath() from vfs_cache.c. > > Here is the thing: > When the MAC Framework mpo_vnode_check_write procedure is called, the > kernel module is trying to retrieve: the path on the disk for the curthread > and the path of the file in which the curthread is attempting to write. At > the point when the program execution reaches the vn_fullpath() for the > resolution of the file's path, the terminal window 'freezes' (actually the > whole system is not responding, the rest ttys stop responding after > entering login credentials). > > For instance, after loading and initializing a MAC kernel module, I am > opening a existing text file using vi to edit it. After inserting some > random text I press ESC key on keyboard and terminal window 'freezes' (at > that moment the mpo_vnode_check_write is called) ( the struct vnode * vp > which is passed to the MAC procedure is valid (not NULL) and type (enum > vtype) is VREG). > > I have investigated this issue and found out the following: > The get_fullpath() is calling the get_fullpath1() where later the > vn_vptocnp() is invoked. > Retrieving the location for the curthread is successful (the full path > returned). > But when the kernel module is making attempt to retrieve the path for the > vp (argument of the mpo_vnode_check_write) the function vn_lock(*vp, > LK_SHARED | LK_RETRY) (line 2191) located in function vn_vptocnp() is > grabbing control forever. > Hard to say off hand, but so far it looks like the vnode is already exclusively locked and now the kernel deadlocks itself by locking it in shared mode. You can easily inspect the state in ddb with show lockedvnods. Are you running the kernel with DEBUG_VFS_LOCKS? What is the purpose of this module in the first place? regular vnode -> path resolution is not guaranteed to work. While it will work most of the time, it is inherently racy problematic in presence of multiple hardlinks. For instance someone else can be modifying the directory tree as you translate back and trick you into thinking the vnode represents a different file. Even if this was not the case, the translation of the sort on each write would be a performance killer. The only possibly working approach I see would attach metadata to the vnode after lookup and then use it. > Below I have copied and pasted the code which performers the path > resolution and the MAC procedure handler: > static int > rw_retreive_data(struct thread * td, struct vnode *dvp, char ** rpath, > char ** curpath, struct sandbox_rule_app ** rule_ptr) > { > [snip] > error = vn_fullpath(td, td->td_proc->p_textvp, curpath, &curfreepath); > [snip] > } > > int sandbox_vnode_check_write(struct ucred *active_cred, > struct > ucred *file_cred, > struct > vnode *vp, > struct > label *vplabel) > { > IS_MODULE_INITED(0) > ASSERT_NULL_R(vp, 0); > > struct sandbox_rule_app * rule_ptr = NULL; > char * rpath = "-"; > char * curpath = "-"; > int error = 0; > > RWLOCK_BLOCK(&sandbox_rules_lock, RWLOCK_READ) > { > > error = rw_retreive_data(curthread, vp, &rpath, &curpath, > &rule_ptr); > If this is using rwlock the code is additionally wrong as vn_fullpath can induce unbound sleep, while the lock at hand only supports bound sleep. -- Mateusz Guzik From owner-freebsd-fs@freebsd.org Tue May 30 20:17:26 2017 Return-Path: Delivered-To: freebsd-fs@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 A9D34BEB6E9 for ; Tue, 30 May 2017 20:17:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8E49177B80 for ; Tue, 30 May 2017 20:17:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4UKHQvc085793 for ; Tue, 30 May 2017 20:17:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 219646] "ls: fts_read: no such file or directory" in zfs snapshot dir Date: Tue, 30 May 2017 20:17:26 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: g_amanakis@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 20:17:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219646 --- Comment #2 from g_amanakis@yahoo.com --- Yes, r319096 resolves it. Any chance of getting this into 11.1-RELEASE sinc= e it is high impact and low risk? --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Tue May 30 21:11:37 2017 Return-Path: Delivered-To: freebsd-fs@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 E6C86BEE0CB for ; Tue, 30 May 2017 21:11:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D539E7A5B5 for ; Tue, 30 May 2017 21:11:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4ULBbpV061406 for ; Tue, 30 May 2017 21:11:37 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 219646] "ls: fts_read: no such file or directory" in zfs snapshot dir Date: Tue, 30 May 2017 21:11:37 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 21:11:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219646 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |avg@FreeBSD.org --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Tue May 30 21:12:41 2017 Return-Path: Delivered-To: freebsd-fs@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 E7D16BEE324 for ; Tue, 30 May 2017 21:12:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D14F97A8E9 for ; Tue, 30 May 2017 21:12:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4ULCfge069062 for ; Tue, 30 May 2017 21:12:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 219646] "ls: fts_read: no such file or directory" in zfs snapshot dir Date: Tue, 30 May 2017 21:12:41 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_file_loc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 21:12:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219646 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://svnweb.freebsd.org/ | |base?view=3Drevision&revis= ion | |=3D319096 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Wed May 31 18:31:30 2017 Return-Path: Delivered-To: freebsd-fs@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 50729B82713 for ; Wed, 31 May 2017 18:31:30 +0000 (UTC) (envelope-from alex@nixd.org) Received: from mail.nixd.org (mail.nixd.org [95.211.160.151]) by mx1.freebsd.org (Postfix) with ESMTP id AC8943502 for ; Wed, 31 May 2017 18:31:29 +0000 (UTC) (envelope-from alex@nixd.org) Received: from spamfilter (spamfilter.jail.localhost [192.168.1.4]) by mail.nixd.org (Postfix) with ESMTP id 93AA62FC1 for ; Wed, 31 May 2017 20:31:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nixd.org; h= user-agent:message-id:references:in-reply-to:organization :subject:subject:from:from:date:date:content-type:content-type :mime-version:received:received; s=default; t=1496255481; bh=2KQ vtr2KEIpi5aEevUKrxOHEZpGHvlKM+ziJMFKVAU8=; b=GaJ7uTKOA08z+cmCHHO qpNDkX9ppHk/dgcKTHU5RPcsXY1oTLLNA4XW8LrcYI5fdM432EAXN5BQIMewuwD1 vKGRyd7GUj/Bv6IZQKdTlB7SEopfFh/+7O3i9b6CkO2uAZVvPoGue+cou1CzmRYk 2dXbRhWt7D/h4Q0ewoGGFUo8= X-Virus-Scanned: amavisd-new at nixd.org Received: from mail.nixd.org ([192.168.1.2]) by spamfilter (nixd.org [192.168.1.4]) (amavisd-new, port 10024) with ESMTP id ootd6nX64aG2 for ; Wed, 31 May 2017 20:31:21 +0200 (CEST) Received: from nixd.org (webserver.jail.localhost [192.168.1.1]) by mail.nixd.org (Postfix) with ESMTPA id D76492FC0 for ; Wed, 31 May 2017 20:31:20 +0200 (CEST) MIME-Version: 1.0 Date: Wed, 31 May 2017 23:31:20 +0500 From: Alexander Morozov To: Freebsd fs Subject: Re: VFS vn_lock function makes system unresponsive when calling vn_fullpath Organization: NiXD In-Reply-To: <2d76399889bb95b75cb6b054c4c68116@nixd.org> References: <38666c423c33a5e1009c106c23aeb218@nixd.org> <2d76399889bb95b75cb6b054c4c68116@nixd.org> Message-ID: X-Sender: alex@nixd.org User-Agent: Roundcube Webmail/1.2.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 May 2017 18:31:30 -0000 Hi Mateusz, Thank you for your response. >> Hard to say off hand, but so far it looks like the vnode is already exclusively locked It seems so. I have added "error = vn_lock(dvp, LK_SHARED | LK_SLEEPFAIL);" to the code of the kernel module before vn_gullpath() and vn_lock has returned error code: EDEADLK 11 /* Resource deadlock avoided */. >> Are you running the kernel with DEBUG_VFS_LOCKS? At the moment no, because I was only suspecting that something wrong with the vnode, but I hoped that the problem was located somewhere in the namecache lookup. Later, I will run kernel with DEBUG_VFS_LOCKS. >> What is the purpose of this module in the first place? It is a clone of the Apple's Sandbox (seatbelts or how it was called). The module performs: mandatory (by choice) integrity control of the executable files and option to apply additional constraints on the executable. The test version of the userland software is almost ready. The tinyscheme scripts are converted to the binary schemes (like apple sandbox does, but in another way to avoid problems with Apple). The rules can be loaded to the module, and testing against the mpo_kld_check_load was successful. This is more like a research and at the same time my personal "security" tool which ideally, should apply on some programs additional constraints and warn the admin/security team in real time if the application is attempting to leave the sandbox (is doing what it was prohibited to do) (i.e like access /etc/rc.conf, /dev/kmem even as root, execute shell), for instance php suddenly performs kldload from /tmp. (I know that this is more "WinNT" approach (Agnitum Outpost with proactive security), for this reason I am not advertising it a lot and probably I will keep source code available online) I need this kernel module because I am running some closed source programs on the server which are "black boxes" and can't be trusted from any point. And for other reasons... Three developers (inc me) are working on the development of the project in their spare time. >> regular vnode -> path resolution is not guaranteed to work Yes, I remember we discussed a bit this problem when I was studying in university. But for development it was more than enough. >>. For instance someone else can be modifying the directory tree as you translate Yes, this is also possible. The plan is to implement other MAC procedures and then decide what to do with vn_fullpath and vnodes in general. My intention was to confirm that vn_fullpath() is a dead end and that the FreeBSD developers know of the potential deadlock problem. To let others know where to look for solution should they experience the same problem. -- Kind Regards, Alexander Morozov > Hi Mateusz, > > Thank you for your response. > >>> Hard to say off hand, but so far it looks like the vnode is already exclusively locked > > It seems so. I have added "error = vn_lock(dvp, LK_SHARED | LK_SLEEPFAIL);" to the code of the kernel module before vn_gullpath() and vn_lock has returned error code: EDEADLK 11 /* Resource deadlock avoided */. > >>> Are you running the kernel with DEBUG_VFS_LOCKS? > > At the moment no, because I was only suspecting that something wrong with the vnode, but I hoped that the problem was located somewhere in the namecache lookup. Later, I will run kernel with DEBUG_VFS_LOCKS. > >>> What is the purpose of this module in the first place? > > It is a clone of the Apple's Sandbox (seatbelts or how it was called). The module performs: mandatory (by choice) integrity control of the executable files and option to apply additional constraints on the executable. The test version of the userland software is almost ready. The tinyscheme scripts are converted to the binary schemes (like apple sandbox does, but in another way to avoid problems with Apple). The rules can be loaded to the module, and testing against the mpo_kld_check_load was successful. > > This is more like a research and at the same time my personal "security" tool which ideally, should apply on some programs additional constraints and warn the admin/security team in real time if the application is attempting to leave the sandbox (is doing what it was prohibited to do) (i.e like access /etc/rc.conf, /dev/kmem even as root, execute shell), for instance php suddenly performs kldload from /tmp. (I know that this is more "WinNT" approach (Agnitum Outpost with proactive security), for this reason I am not advertising it a lot and probably I will keep source code available online) > > I need this kernel module because I am running some closed source programs on the server which are "black boxes" and can't be trusted from any point. And for other reasons... Three developers (inc me) are working on the development of the project in their spare time. > >>> regular vnode -> path resolution is not guaranteed to work > > Yes, I remember we discussed a bit this problem when I was studying in university. But for development it was more than enough. > >>> . For instance someone else can be modifying the directory tree as you translate > > Yes, this is also possible. The plan is to implement other MAC procedures and then decide what to do with vn_fullpath and vnodes in general. > > My intention was to confirm that vn_fullpath() is a dead end and that the FreeBSD developers know of the potential deadlock problem. To let others know where to look for solution should they experience the same problem. > > -- > > Kind Regards, > Alexander Morozov > > Mateusz Guzik писал 2017-05-31 00:27: > On Tue, May 30, 2017 at 4:42 PM, Alexander Morozov wrote: > > Hi, > > At the moment I am developing a kernel module based on MAC Framework which is invoking a vn_fullpath() from vfs_cache.c. > > Here is the thing: > When the MAC Framework mpo_vnode_check_write procedure is called, the kernel module is trying to retrieve: the path on the disk for the curthread and the path of the file in which the curthread is attempting to write. At the point when the program execution reaches the vn_fullpath() for the resolution of the file's path, the terminal window 'freezes' (actually the whole system is not responding, the rest ttys stop responding after entering login credentials). > > For instance, after loading and initializing a MAC kernel module, I am opening a existing text file using vi to edit it. After inserting some random text I press ESC key on keyboard and terminal window 'freezes' (at that moment the mpo_vnode_check_write is called) ( the struct vnode * vp which is passed to the MAC procedure is valid (not NULL) and type (enum vtype) is VREG). > > I have investigated this issue and found out the following: > The get_fullpath() is calling the get_fullpath1() where later the vn_vptocnp() is invoked. > Retrieving the location for the curthread is successful (the full path returned). > But when the kernel module is making attempt to retrieve the path for the vp (argument of the mpo_vnode_check_write) the function vn_lock(*vp, LK_SHARED | LK_RETRY) (line 2191) located in function vn_vptocnp() is grabbing control forever. > > Hard to say off hand, but so far it looks like the vnode is already exclusively locked and now the kernel deadlocks itself by locking it in shared mode. You can easily inspect the state in ddb with show lockedvnods. > > Are you running the kernel with DEBUG_VFS_LOCKS? > > What is the purpose of this module in the first place? > > regular vnode -> path resolution is not guaranteed to work. While it will work most of the time, it is inherently racy problematic in presence of multiple hardlinks. For instance someone else can be modifying the directory tree as you translate back and trick you into thinking the vnode represents a different file. Even if this was not the case, the translation of the sort on each write would be a performance killer. > > The only possibly working approach I see would attach metadata to the vnode after lookup and then use it. > Below I have copied and pasted the code which performers the path resolution and the MAC procedure handler: > static int > rw_retreive_data(struct thread * td, struct vnode *dvp, char ** rpath, char ** curpath, struct sandbox_rule_app ** rule_ptr) > { > [snip] error = vn_fullpath(td, td->td_proc->p_textvp, curpath, &curfreepath); > [snip] } > > int sandbox_vnode_check_write(struct ucred *active_cred, > struct ucred *file_cred, > struct vnode *vp, > struct label *vplabel) > { > IS_MODULE_INITED(0) > ASSERT_NULL_R(vp, 0); > > struct sandbox_rule_app * rule_ptr = NULL; > char * rpath = "-"; > char * curpath = "-"; > int error = 0; > > RWLOCK_BLOCK(&sandbox_rules_lock, RWLOCK_READ) > { > > error = rw_retreive_data(curthread, vp, &rpath, &curpath, &rule_ptr); > > If this is using rwlock the code is additionally wrong as vn_fullpath can induce unbound sleep, while the lock at hand only supports bound sleep. > -- > Mateusz Guzik Links: ------ [1] http://gmail.com From owner-freebsd-fs@freebsd.org Wed May 31 20:04:45 2017 Return-Path: Delivered-To: freebsd-fs@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 A5FADB8880A for ; Wed, 31 May 2017 20:04:45 +0000 (UTC) (envelope-from kisscoolandthegangbang@hotmail.fr) Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-oln040092071036.outbound.protection.outlook.com [40.92.71.36]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 31B88668C5 for ; Wed, 31 May 2017 20:04:44 +0000 (UTC) (envelope-from kisscoolandthegangbang@hotmail.fr) Received: from DB5EUR03FT045.eop-EUR03.prod.protection.outlook.com (10.152.20.53) by DB5EUR03HT069.eop-EUR03.prod.protection.outlook.com (10.152.20.212) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1101.12; Wed, 31 May 2017 20:04:42 +0000 Received: from DBXPR05MB157.eurprd05.prod.outlook.com (10.152.20.60) by DB5EUR03FT045.mail.protection.outlook.com (10.152.21.164) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1101.12 via Frontend Transport; Wed, 31 May 2017 20:04:42 +0000 Received: from DBXPR05MB157.eurprd05.prod.outlook.com ([fe80::8121:96da:8303:3a63]) by DBXPR05MB157.eurprd05.prod.outlook.com ([fe80::8121:96da:8303:3a63%27]) with mapi id 15.01.1124.016; Wed, 31 May 2017 20:04:42 +0000 From: kc atgb To: "freebsd-fs@freebsd.org" Subject: Re: Problem with zpool remove of log device Thread-Topic: Problem with zpool remove of log device Thread-Index: AQHS2kkkWE5shmvvSUeFr52IoccjVw== Date: Wed, 31 May 2017 20:04:42 +0000 Message-ID: References: <9188a169-cd81-f64d-6b9e-0e3c6b4af1bb@wasikowski.net> In-Reply-To: <9188a169-cd81-f64d-6b9e-0e3c6b4af1bb@wasikowski.net> Accept-Language: fr-FR, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=none action=none header.from=hotmail.fr; x-incomingtopheadermarker: OriginalChecksum:EC7AC1C015227AFB2F7CF62440A66A90105695E7E2AC856091624505B94CC504; UpperCasedChecksum:7CAB9416C1B950F7601C75AD116A74FB8324026DAA97D542BEF0DF59AF3F4381; SizeAsReceived:8075; Count:42 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; DB5EUR03HT069; 24:3rddpmiNQ89yfk8VQNs/1Kiu/ohJv30U/12JOa9cp7NdEf5JvEAjYhCTNg+OZVqqmcbBXZERYSW5zDIbdblG36FlLwptITdUNuT9Ti579hE=; 7:c/0n+758ELHNUmz+V4QIW+fX/bzoV+wUV/MYJwNwk874sywZlQRlkg4uCpyV7snSLL86HuboGQqKWLWpKY8dJvaVfNjmB0XxzljMTSwRtjXI4Wu/h4Uq7HJ2NUfJT4hj1e+fPGzUM7Q+qtwiIfT0qH2MiARlSgTiRyAE6RqPMNHMmi2KGh1tTyjEueKkAA+XyjfGYvYxPuWvHOoWoJZKL1xFr8p9DMr+RM11Uq0SdfiBp2+Q5cEyO5sTFKWjiOICY8M9zltZaxPlOuaJHkrm9PR/jxtiiW9PPsfmvm8mwh/tpQurkeSvBZzYNaq4xfw2 x-incomingheadercount: 42 x-eopattributedmessage: 0 x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:DB5EUR03HT069; H:DBXPR05MB157.eurprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; x-ms-traffictypediagnostic: DB5EUR03HT069: x-ms-office365-filtering-correlation-id: 10740008-ebea-45e5-53a3-08d4a8604685 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:DB5EUR03HT069; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700073)(100105000095)(100000701073)(100105300095)(100000702073)(100105100095)(444000031); SRVR:DB5EUR03HT069; BCL:0; PCL:0; RULEID:(100000800073)(100110000095)(100000801073)(100110300095)(100000802073)(100110100095)(100000803073)(100110400095)(100000804073)(100110200095)(100000805073)(100110500095); SRVR:DB5EUR03HT069; x-forefront-prvs: 0324C2C0E2 spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-2" Content-ID: <6A49541CE18E4342B01D268AE6EF8A7B@eurprd05.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-originalarrivaltime: 31 May 2017 20:04:42.6260 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5EUR03HT069 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 May 2017 20:04:45 -0000 Le Fri, 26 May 2017 09:40:06 +0000, =A3ukasz W=B1sikowski a =E9crit : > Hi, >=20 > I cant remove log device from pool - operation ends ok, but log device > is still in the pool (bug?). >=20 > # uname -a > FreeBSD xxx.yyy.com 11.0-STABLE FreeBSD 11.0-STABLE #0 r316543: Thu Apr > 6 08:22:43 CEST 2017 root@xxx.yyy.com:/usr/obj/usr/src/sys/YYY amd64 >=20 > # zpool status tank > pool: tank > state: ONLINE > status: One or more devices are configured to use a non-native block size= . > Expect reduced performance. > action: Replace affected devices with devices that support the > configured block size, or migrate data to a properly configured > pool. > scan: scrub repaired 0 in 22h21m with 0 errors on Thu May 25 02:26:36 2= 017 > config: >=20 > NAME STATE READ WRITE CKSUM > tank ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > ada2p3 ONLINE 0 0 0 > ada3p3 ONLINE 0 0 0 > logs > mirror-1 ONLINE 0 0 0 > gpt/tankssdzil0 ONLINE 0 0 0 block size: > 512B configured, 4096B native > gpt/tankssdzil1 ONLINE 0 0 0 block size: > 512B configured, 4096B native >=20 > errors: No known data errors >=20 > When I try to remove log device operation ends without errors: >=20 > # zpool remove tank mirror-1; echo $? > 0 >=20 > But the log device is still there: >=20 > # zpool status tank > pool: tank > state: ONLINE > status: One or more devices are configured to use a non-native block size= . > Expect reduced performance. > action: Replace affected devices with devices that support the > configured block size, or migrate data to a properly configured > pool. > scan: scrub repaired 0 in 22h21m with 0 errors on Thu May 25 02:26:36 2= 017 > config: >=20 > NAME STATE READ WRITE CKSUM > tank ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > ada2p3 ONLINE 0 0 0 > ada3p3 ONLINE 0 0 0 > logs > mirror-1 ONLINE 0 0 0 > gpt/tankssdzil0 ONLINE 0 0 0 block size: > 512B configured, 4096B native > gpt/tankssdzil1 ONLINE 0 0 0 block size: > 512B configured, 4096B native >=20 > errors: No known data errors >=20 >=20 > I'd like to remove it - how should I proceed? >=20 >=20 Hi, I had a problem like this not so long ago.=20 I thought maybe it was something with my installation and because that I ha= ve an older version of FreeBSD and by the same occasion older version of zf= s.=20 I found some similar cases but for openzfs on linux and if I'm not wrong op= ensolaris. I know now that not the only one on FreeBSD.=20 It was something with zfs thinkink that writes are not synced from log to d= isks, and it can't remove the device.=20 How is your zpool iostat -v output after you offline the log device(s) ? Is= there any persistent data on allocated row ? K.=20 From owner-freebsd-fs@freebsd.org Wed May 31 21:22:30 2017 Return-Path: Delivered-To: freebsd-fs@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 16A20B94DC1 for ; Wed, 31 May 2017 21:22:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0440E6A284 for ; Wed, 31 May 2017 21:22:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4VLMTx0040437 for ; Wed, 31 May 2017 21:22:29 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 219688] [ZFS] zfs rename of mountpoint that is nfs shared leaves old NFS configuration active and unremoveable Date: Wed, 31 May 2017 21:22:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 May 2017 21:22:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219688 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Jun 1 11:50:09 2017 Return-Path: Delivered-To: freebsd-fs@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 87602AFADAD for ; Thu, 1 Jun 2017 11:50:09 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A1F7F76CD8; Thu, 1 Jun 2017 11:50:08 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA24532; Thu, 01 Jun 2017 14:49:59 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1dGOc3-000Pgl-Af; Thu, 01 Jun 2017 14:49:59 +0300 Subject: Re: Strange behavior of .zfs/snapshot/* directories in respect to ".." path. To: lev@FreeBSD.org, freebsd-fs@FreeBSD.org References: <1acc5917-f10f-b18a-50e0-84661173e85d@FreeBSD.org> <1601598008.20170529015948@serebryakov.spb.ru> <8138588b-4b03-16d9-77b6-2a3e3444997d@FreeBSD.org> <1279842496.20170529132006@serebryakov.spb.ru> <01c59f49-f45a-b02f-31f1-88c130609094@FreeBSD.org> <5d9dbe2e-9d51-0df2-1280-25ccbe710900@FreeBSD.org> From: Andriy Gapon Message-ID: Date: Thu, 1 Jun 2017 14:49:22 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <5d9dbe2e-9d51-0df2-1280-25ccbe710900@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 11:50:09 -0000 On 29/05/2017 15:43, Lev Serebryakov wrote: > On 29.05.2017 13:22, Andriy Gapon wrote: > >>> Now, as r319091 was committed, I'm building new fresh kernel. >> Thank you. Please let me know how it goes. > I don't have any problems with r319091 + patch for "..". > The latter patch is in stable/11 now as well. r319415. -- Andriy Gapon From owner-freebsd-fs@freebsd.org Thu Jun 1 11:50:18 2017 Return-Path: Delivered-To: freebsd-fs@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 45514AFADC9 for ; Thu, 1 Jun 2017 11:50:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3184376D26 for ; Thu, 1 Jun 2017 11:50:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v51BoHUU083619 for ; Thu, 1 Jun 2017 11:50:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 219646] "ls: fts_read: no such file or directory" in zfs snapshot dir Date: Thu, 01 Jun 2017 11:50:17 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: component bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 11:50:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219646 Andriy Gapon changed: What |Removed |Added ---------------------------------------------------------------------------- Component|bin |kern Status|New |Closed Resolution|--- |FIXED --- Comment #3 from Andriy Gapon --- This is in stable/11 now, base r319415. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Sat Jun 3 22:43:29 2017 Return-Path: Delivered-To: freebsd-fs@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 6B0B3BFA5A2 for ; Sat, 3 Jun 2017 22:43:29 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3E5B1805CB; Sat, 3 Jun 2017 22:43:29 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 58523A3C4; Sat, 3 Jun 2017 22:43:28 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id D9E6B7340; Sat, 3 Jun 2017 22:43:26 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id dtwJIa9ry7iD; Sat, 3 Jun 2017 22:43:17 +0000 (UTC) To: Rick Macklem DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com 3861B733A Cc: FreeBSD FS From: Bryan Drewery Subject: NFS panic: newnfs_copycred: negative nfsc_ngroups Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Organization: FreeBSD Message-ID: <2b7a77df-8291-d399-6d1f-c454fbb2a5d9@FreeBSD.org> Date: Sat, 3 Jun 2017 15:43:00 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qLkRtHPOE1ng6AK76SLBOBv3Q07x8Mkgg" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jun 2017 22:43:29 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --qLkRtHPOE1ng6AK76SLBOBv3Q07x8Mkgg Content-Type: multipart/mixed; boundary="7jvj01t9qTfBf6Ok3GJkfXWHsugOSlKGp"; protected-headers="v1" From: Bryan Drewery To: Rick Macklem Cc: FreeBSD FS Message-ID: <2b7a77df-8291-d399-6d1f-c454fbb2a5d9@FreeBSD.org> Subject: NFS panic: newnfs_copycred: negative nfsc_ngroups --7jvj01t9qTfBf6Ok3GJkfXWHsugOSlKGp Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Last reported here but I forgot to follow-up https://lists.freebsd.org/pipermail/freebsd-current/2013-July/042996.html= I still get this quite often. Server is: 10.2-RELEASE-p2 Client is: 12.0-CURRENT #5 r318116M mount is (no soft or intr since 2013): > tank:/tank/distfiles/freebsd /mnt/distfiles = nfs rw,bg,noatime,rsize=3D65536,wsize=3D65536,readahead=3D8,= nfsv4,rdirplus 0 0 I have a core for debugging... > (kgdb) bt > #0 __curthread () at ./machine/pcpu.h:232 > #1 doadump (textdump=3D1) at /usr/src/sys/kern/kern_shutdown.c:318 > #2 0xffffffff803abf3c in db_fncall_generic (addr=3D, rv= =3D, nargs=3D, args=3D) at /= usr/src/sys/ddb/db_command.c:581 > #3 db_fncall (dummy1=3D, dummy2=3D, dumm= y3=3D, dummy4=3D) at /usr/src/sys/ddb/db_co= mmand.c:629 > #4 0xffffffff803abaaf in db_command (last_cmdp=3D, cmd_= table=3D, dopager=3D) at /usr/src/sys/ddb/d= b_command.c:453 > #5 0xffffffff803ab7e4 in db_command_loop () at /usr/src/sys/ddb/db_com= mand.c:506 > #6 0xffffffff803ae89f in db_trap (type=3D, code=3D) at /usr/src/sys/ddb/db_main.c:248 > #7 0xffffffff80a9fda3 in kdb_trap (type=3D3, code=3D-61456, tf=3D) at /usr/src/sys/kern/subr_kdb.c:654 > #8 0xffffffff80ee9286 in trap (frame=3D0xfffffe355f840540) at /usr/src= /sys/amd64/amd64/trap.c:537 > #9 > #10 kdb_enter (why=3D0xffffffff81455661 "panic", msg=3D)= at /usr/src/sys/kern/subr_kdb.c:444 > #11 0xffffffff80a5d759 in vpanic (fmt=3D, ap=3D0xfffffe3= 55f8406d0) at /usr/src/sys/kern/kern_shutdown.c:772 > #12 0xffffffff80a5d59f in _kassert_panic (fatal=3D1, fmt=3D0xffffffff81= 434d8b "newnfs_copycred: negative nfsc_ngroups") at /usr/src/sys/kern/ker= n_shutdown.c:669 > #13 0xffffffff80946ec2 in newnfs_copycred (nfscr=3D0xfffff8047b3eb530, = cr=3D0xfffff80122cfa500) at /usr/src/sys/fs/nfs/nfs_commonport.c:244 > #14 0xffffffff8094bddc in nfscl_getstateid (vp=3D, nfhp=3D= 0xfffff80501233902 "\233\262\tM\336\006\236\313\n", fhlen=3D28, mode=3D1,= fords=3D, cred=3D, p=3D, st= ateidp=3D, lckpp=3D) at /usr/src/sys/fs/nfs= client/nfs_clstate.c:630 > #15 0xffffffff8095ca88 in nfsrpc_read (vp=3D0xfffff8030bc209c0, uiop=3D= 0xfffffe355f840af8, cred=3D0xfffff80122cfa500, p=3D0x0, nap=3D0xfffffe355= f8409d0, attrflagp=3D0xfffffe355f840aa4, stuff=3D) at /usr= /src/sys/fs/nfsclient/nfs_clrpcops.c:1396 > #16 0xffffffff8096b90a in ncl_readrpc (vp=3D0xfffff8030bc209c0, uiop=3D= 0xfffffe355f840af8, cred=3D0xfffff801b4913300) at /usr/src/sys/fs/nfsclie= nt/nfs_clvnops.c:1375 > #17 0xffffffff80976656 in ncl_doio (vp=3D0xfffff8030bc209c0, bp=3D0xfff= ffe349a268750, cr=3D, td=3D0x0, called_from_strategy=3D) at /usr/src/sys/fs/nfsclient/nfs_clbio.c:1643 > #18 0xffffffff80978694 in nfssvc_iod (instance=3D) at /u= sr/src/sys/fs/nfsclient/nfs_clnfsiod.c:302 > #19 0xffffffff80a1e394 in fork_exit (callout=3D0xffffffff80978420 , arg=3D0xffffffff81c7de64 , frame=3D0xfffffe35= 5f840c00) at /usr/src/sys/kern/kern_fork.c:1038 > #20 > (kgdb) p *nfscr > $3 =3D {nfsc_uid =3D 3735929054, nfsc_groups =3D {3735929054 }, nfsc_ngroups =3D -559038242} > (kgdb) frame 17 > #17 0xffffffff80976656 in ncl_doio (vp=3D0xfffff8030bc209c0, bp=3D0xfff= ffe349a268750, cr=3D, td=3D0x0, called_from_strategy=3D) at /usr/src/sys/fs/nfsclient/nfs_clbio.c:1643 > (kgdb) p vp->v_mount->mnt_stat.f_mntonname > $8 =3D "/mnt/distfiles", '\000' I had some bogus -domain in my nfsuserd options on the client that I removed after the recent panic. Not sure if it is relevant. --=20 Regards, Bryan Drewery --7jvj01t9qTfBf6Ok3GJkfXWHsugOSlKGp-- --qLkRtHPOE1ng6AK76SLBOBv3Q07x8Mkgg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJZMzt4AAoJEDXXcbtuRpfPF2gH/0iXNZcbl2JRglqrYQAQLKR5 WN2zbOEIrgaHjyaTiXIad+HWMgSmnNQCMm3Z5TeX5nHDCDnwvCeVVflGZQQ28iYo lNLMtcsTMpFkykyJRX9YhgxMKY2zqv9CwGR/ZIkLznM4q6V43L8jLFXEVflf5fkn OsjjqWjh9HfGVrhb++D135SCvVM3Pmyp5wgO5r2j9IpkTly1aOs3RcNNidDPoPr2 Zc2X5xU7aNA01WLJbhVSQ18BHZtyyBgkJFeDIA0xxZVQV86q3uf1jV4uMlmfX9l1 IlCxPV0X/JkGsti3Z6zr5UWfcrSz0F12fMAbFa4crzqYEnQKDOPJ6/m9Yd6nS0M= =l0vg -----END PGP SIGNATURE----- --qLkRtHPOE1ng6AK76SLBOBv3Q07x8Mkgg--