Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Aug 2000 17:30:32 -0600
From:      "Kenneth D. Merry" <ken@kdm.org>
To:        current@FreeBSD.ORG
Cc:        mckusick@mckusick.com
Subject:   softupdates panic, possibly related to snapshots
Message-ID:  <20000814173032.A74181@panzer.kdm.org>

next in thread | raw e-mail | index | archive | help

I had a panic today on a -current box from early August 3rd.  This is all I
got out of the crash dump:

==============================================================================
# gdb -k /a/ken/perforce/cam/sys/compile/roadwarrior/kernel.debug vmcore.2 
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
IdlePTD 3723264
initial pcb at 2fc240
panicstr: handle_workitem_freeblocks: block count
panic messages:
---
dmesg: kvm_read: invalid address (f0403000)
---
#0  boot (howto=Cannot access memory at address 0xc9394dec.
) at ../../kern/kern_shutdown.c:303
303                     dumppcb.pcb_cr3 = rcr3();
(kgdb) where
#0  boot (howto=Cannot access memory at address 0xc9394dec.
) at ../../kern/kern_shutdown.c:303
Cannot access memory at address 0xc9394de4.
(kgdb) 
==============================================================================

All local filesystems on the machine, except /, are running softupdates:


==============================================================================
{roadwarrior:/usr/home/ken:2:0} df
Filesystem       1K-blocks     Used    Avail Capacity  Mounted on
/dev/da0s2a          63503    52026     6397    89%    /
/dev/da0s2e         198399   153494    29034    84%    /var
/dev/da0s2f        3290562  2961377    65941    98%    /usr
/dev/da1s1a        8648870  7154983   801978    90%    /a
procfs                   4        4        0   100%    /proc
pluto:/usr/local   4065262  1936074  1803968    52%    /usr/local2
{roadwarrior:/usr/home/ken:3:0} mount
/dev/da0s2a on / (ufs, NFS exported, local, writes: sync 8 async 51, reads: sync 497 async 68)
/dev/da0s2e on /var (ufs, local, soft-updates, writes: sync 146 async 2399, reads: sync 94 async 1)
/dev/da0s2f on /usr (ufs, NFS exported, local, soft-updates, writes: sync 2 async 160, reads: sync 652 async 93)
/dev/da1s1a on /a (ufs, NFS exported, local, soft-updates, writes: sync 2 async 87, reads: sync 546 async 207)
procfs on /proc (procfs, local)
pluto:/usr/local on /usr/local2 (nfs)
{roadwarrior:/usr/home/ken:4:0} 
==============================================================================

The crash happened shortly after I created, mounted and removed a snapshot.
Here's what I did, more or less:

mkdir /var/snapshots
mount -u -o snapshot /var/snapshots/snap1 /var
vnconfig -c /dev/vn0c /var/snapshots/snap1
mount /dev/vn0c /mnt
ls /mnt/...
[ a little more looking around ]
umount /mnt
vnconfig -u /dev/vn0c
cd /var/snapshots
rm snap1
cd
rmdir /var/snapshots

Then I went back to doing other stuff, and a minute or two later, the
machine rebooted.  I didn't think it had time to generate a 128MB crash
dump, but evidently it did.

If anyone wants more information, just let me know, although I'm not sure if
I'm really eager to panic the machine again. :)  (I've got a test box
that would be better for testing, though.)

Ken
-- 
Kenneth Merry
ken@kdm.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000814173032.A74181>