Date: Wed, 25 Mar 2015 15:44:55 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 198208] FreeBSD 10.1 multiple kernel panics 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-198208-8-T5KalMVA7l>