From owner-freebsd-fs@freebsd.org Tue Apr 30 16:18:09 2019 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A0D4C1596D63 for ; Tue, 30 Apr 2019 16:18:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 23C7781860 for ; Tue, 30 Apr 2019 16:18:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id DB6991596D62; Tue, 30 Apr 2019 16:18:08 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9DE11596D61 for ; Tue, 30 Apr 2019 16:18:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6941C8185E for ; Tue, 30 Apr 2019 16:18:08 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id A18A398B4 for ; Tue, 30 Apr 2019 16:18:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x3UGI781030958 for ; Tue, 30 Apr 2019 16:18:07 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3UGI7lA030957 for fs@FreeBSD.org; Tue, 30 Apr 2019 16:18:07 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 236220] ZFS vnode deadlock on zfs_mknode Date: Tue, 30 Apr 2019 16:18:07 +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: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ncrogers@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2019 16:18:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236220 --- Comment #24 from ncrogers@gmail.com --- (In reply to Dennis Noordsij from comment #23) Yes, I have a few systems that have about a 6 week uptime now after applying the patch, and many more running the same patch with uptimes less than a mo= nth because that's about when I started upgrading more systems. It does seem to take up to a few weeks to manifest itself but I feel like I have enough sys= tems running this now that it would have happened. In my experience it doesn't seem to matter if its a small workload or a huge workload, eventually it strikes. My guess is the problem is unique to somet= hing strange with how PostgreSQL handles its WAL but I have no idea what that wo= uld be. I have full_page_writes OFF, synchronous_commit OFF, and fsync ON in my postgresql conf. Running PostgreSQL 11.2. I will definitely report back if I witness a hang/crash. Perhaps it would be useful for someone to open up an issue with PostgreSQL? I am less familiar = with their bug reporting process. But given that there is definitively a bug in a feature borrowed from ZoL that was later fixed in ZoL upstream, it seems l= ike this is more of a FreeBSD problem, so I am not sure if PostgreSQL devs will have much to say other than to perhaps help pinpoint why this is only happe= ning to postgres users? --=20 You are receiving this mail because: You are the assignee for the bug.=