Date: Tue, 30 Apr 2019 16:18:07 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 236220] ZFS vnode deadlock on zfs_mknode Message-ID: <bug-236220-3630-dve76DB2fy@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-236220-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-236220-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236220-3630-dve76DB2fy>