From owner-freebsd-fs@freebsd.org  Sat May  7 23:16:49 2016
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 97824B321EC
 for <freebsd-fs@mailman.ysv.freebsd.org>; Sat,  7 May 2016 23:16:49 +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 87E1B1C7B
 for <freebsd-fs@FreeBSD.org>; Sat,  7 May 2016 23:16:49 +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 u47NGnaa076790
 for <freebsd-fs@FreeBSD.org>; Sat, 7 May 2016 23:16:49 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 208691] "panic: ffs_valloc: dup alloc" as soon as UFS root
 partition is mounted
Date: Sat, 07 May 2016 23:16:49 +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.2-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: mckusick@FreeBSD.org
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: Not A Bug
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-208691-3630-tqTCj1tzs9@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-208691-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-208691-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.22
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: Sat, 07 May 2016 23:16:49 -0000

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

Kirk McKusick <mckusick@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Closed
         Resolution|---                         |Not A Bug

--- Comment #4 from Kirk McKusick <mckusick@FreeBSD.org> ---
I am closing this bug as it is triggered by disks running in an unreliable
mode. As such there is no change called for in the software, though one can
legitimately argue that the default should be to configure disks to run with
`write cache disabled' so that they will be reliable. FreeBSD ran for a whi=
le
with this default, but for many disks the performance was abysmal, so the
default reverted back to unreliable. Most disks support tag queuing today w=
hich
does not suffer poor performance from `write cache disabled', so perhaps it=
 is
time to revisit this default. But that is not a topic for this report.

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