From owner-freebsd-fs@freebsd.org  Tue Dec 12 20:56:24 2017
Return-Path: <owner-freebsd-fs@freebsd.org>
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 DA555E84B87
 for <freebsd-fs@mailman.ysv.freebsd.org>; Tue, 12 Dec 2017 20:56:24 +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 C730C72AA0
 for <freebsd-fs@FreeBSD.org>; Tue, 12 Dec 2017 20:56:24 +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 vBCKuOOQ088578
 for <freebsd-fs@FreeBSD.org>; Tue, 12 Dec 2017 20:56:24 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 224292] processes are hanging in state ufs / possible deadlock
 in file system
Date: Tue, 12 Dec 2017 20:56:24 +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: wosch@FreeBSD.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-224292-3630-SmS6q46v6J@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-224292-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-224292-3630@https.bugs.freebsd.org/bugzilla/>
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.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Dec 2017 20:56:25 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224292

Wolfram Schneider <wosch@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |In Progress

--- Comment #3 from Wolfram Schneider <wosch@FreeBSD.org> ---
Hi Kirk,

thanks for the fast response. I can run the tests again and see if the mach=
ine
survives the next 3 days.

I'm wondering if we have a simple test program to trigger this bug?=20

Any suggestion to tune dirhash, to get the the broken lock faster?

my current setup:
sysctl  -a|egrep vfs.ufs.dirhash
vfs.ufs.dirhash_reclaimpercent: 10
vfs.ufs.dirhash_lowmemcount: 188
vfs.ufs.dirhash_docheck: 0
vfs.ufs.dirhash_mem: 510163
vfs.ufs.dirhash_maxmem: 2097152
vfs.ufs.dirhash_minsize: 2560

--=20
You are receiving this mail because:
You are the assignee for the bug.=