From owner-freebsd-bugs@FreeBSD.ORG  Sun Nov 23 06:45:37 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 68333FFD
 for <freebsd-bugs@FreeBSD.org>; Sun, 23 Nov 2014 06:45:37 +0000 (UTC)
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 4FB9FD66
 for <freebsd-bugs@FreeBSD.org>; Sun, 23 Nov 2014 06:45:37 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sAN6jbOv050767
 for <freebsd-bugs@FreeBSD.org>; Sun, 23 Nov 2014 06:45:37 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 195278] gjournal UFS: svn update /usr/ports panics with corrupt
 directory emulators/aqemu/files missing `.' and `..'
Date: Sun, 23 Nov 2014 06:45:37 +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.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kennethsalerno@yahoo.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-195278-8-CGehk8uily@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-195278-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-195278-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.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Nov 2014 06:45:37 -0000

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

--- Comment #3 from Kenneth Salerno <kennethsalerno@yahoo.com> ---
Seems to be caused by vfs.unmapped_buf_allowed=1, even though this is a bare
metal laptop and not a VM as was reported in the 10 errata. Maybe what I have
in common with FreeBSD in a VM is small amount of RAM on my laptop and
vfs.unmapped_bufspace is too large for high I/O?

Also, when I changed vfs.unmapped_buf_allowed to 0 and rebooted there were
further file system corruptions detected during use that were not detected
previously when vfs.unmapped_buf_allowed was set to 1, not sure if this is a
coincidence.

After fsdb clri, fsck -fy, fsck -fy, I was able to run svn update /usr/ports
without an error.

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