Date: Thu, 9 Oct 2008 21:18:21 -0700 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: Walter Venable <walt@relnor.com> Cc: freebsd-questions@freebsd.org Subject: Re: Portsnap causes system to reboot Message-ID: <20081010041821.GA22243@icarus.home.lan> In-Reply-To: <48EE7D9E.9060806@relnor.com> References: <8dfae1c10810090938k471f82f0j46caed0514e5b5ac@mail.gmail.com> <20081009164424.GA9081@icarus.home.lan> <48EE77ED.1080306@relnor.com> <48EE7D9E.9060806@relnor.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 10, 2008 at 12:54:38AM +0300, Walter Venable wrote: > >> I found this: $ cat /var/crash/ >> ..minfreboundsçinfo.0ç >> >> vmcore.0zinfo.vmcore.1zinfo.vmcore.2zinfo.vmcore.3zinfo.vmcore.4zinfo.vmcore.5zinfo.vmcore.6zinfo.7vmcore.7zÀ >> >> >> Any idea what that means? > Yes, I'm tired, and I did cat on a directory. I found this in vmcore.7: > > <118>Checking for core dump on /dev/ad4s1b... > <118>savecore: reboot after panic: ffs_clusteralloc: map mismatch > <118>Oct 9 11:16:26 freebsd savecore: reboot after panic: > ffs_clusteralloc: map mismatch > <118>savecore: writing core to vmcore.6 Please reboot your machine into single-user mode, and run "fsck -y". I'm betting there's some filesystem corruption. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081010041821.GA22243>