From owner-freebsd-bugs@FreeBSD.ORG  Wed Mar 25 15:44:55 2015
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 8D90CA8B
 for <freebsd-bugs@FreeBSD.org>; Wed, 25 Mar 2015 15:44:55 +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 73B568E6
 for <freebsd-bugs@FreeBSD.org>; Wed, 25 Mar 2015 15:44:55 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2PFit1B069335
 for <freebsd-bugs@FreeBSD.org>; Wed, 25 Mar 2015 15:44:55 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 198208] FreeBSD 10.1 multiple kernel panics
Date: Wed, 25 Mar 2015 15:44:55 +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 Many People
X-Bugzilla-Who: lists.dan@gmail.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-198208-8-T5KalMVA7l@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-198208-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-198208-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: Wed, 25 Mar 2015 15:44:55 -0000

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

--- Comment #4 from Dan <lists.dan@gmail.com> ---

The hardware is a Dell R710.

I have not tried fsck by hand.  It has been doing background fsck after the
crashes since I disabled the journal.   I was under the impression that fsck
was not really necessary with FFS and soft updates.  I can do a fsck later
today.

# mount -v
/dev/mfid0s1a on / (ufs, NFS exported, local, soft-updates, writes: sync 0
async 290424, reads: sync 14443 async 748, fsid a527ac54915e0c04)
devfs on /dev (devfs, local, multilabel, fsid 00ff007171000000)
procfs on /proc (procfs, local, fsid 01ff000202000000)
/dev/mfid0s1d on /home (ufs, local, soft-updates, writes: sync 38 async 148,
reads: sync 80 async 35, fsid a627ac54c8732378)
/dev/mfid0s1e on /var (ufs, local, soft-updates, writes: sync 734986 async
1149177, reads: sync 8517 async 4503, fsid a627ac548e8fd108)
/dev/mfid0s1f on /opt (ufs, local, soft-updates, writes: sync 161 async 1649,
reads: sync 574 async 68, fsid a627ac54c4f566ef)
/dev/mfid0s1g on /space (ufs, local, soft-updates, writes: sync 2033 async
17366, reads: sync 90145 async 30234, fsid 13bf2a50d8123d8a)
/dev/md0 on /var/tmp/vscan (ufs, local, soft-updates, writes: sync 393738 async
251122, reads: sync 18 async 0, fsid bdc90f5599002a1e)

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