From owner-freebsd-bugs@freebsd.org  Fri Dec  4 13:47:04 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 6BFC8A41912
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Fri,  4 Dec 2015 13:47:04 +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 578611D24
 for <freebsd-bugs@FreeBSD.org>; Fri,  4 Dec 2015 13:47:04 +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 tB4Dl4qW028111
 for <freebsd-bugs@FreeBSD.org>; Fri, 4 Dec 2015 13:47:04 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 178997] [vfs] [patch] Heavy disk I/O may hang system
Date: Fri, 04 Dec 2015 13:47:02 +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: unspecified
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: pr@tns.cz
X-Bugzilla-Status: In Progress
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-178997-8-erY5xm3GW8@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-178997-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-178997-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Dec 2015 13:47:04 -0000

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

pr@tns.cz changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pr@tns.cz

--- Comment #16 from pr@tns.cz ---
(In reply to rainer from comment #15)

We seem to experience this problem independently too (tested on 10.2-RELEASE
and 10.1-RELEASE-p21). In the testing environment the system behaves as
described by rainer. In production, the symptoms seem to be the same (but the
traffic is not generated artificially).

Is there any progress or plans about this issue?

Klaus, please, did you solve the problem? 

Thanks in advance, Pavel

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