Date: Thu, 17 May 2007 15:00:27 +0200 From: Peter Schuller <peter.schuller@infidyne.com> To: freebsd-fs@FreeBSD.org Cc: Pawel Jakub Dawidek <pjd@FreeBSD.org> Subject: ZFS panic: solaris assert: arc_buf_remove_buf(db->db_buf, db) == 0 Message-ID: <464C51EB.4050609@infidyne.com>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig3B5F26B846054F8EFC18E4CA Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello, I am experiencing a panic that I do not believe to have been discussed already. It is being triggered while rsync:ing a directory hierarchy from another machine over ssh onto a 6 drive raidz2 pool. The transfer consists mostly of large files (rather than a huge amount of small files). I seem to be getting this panic within a few hours of starting or resuming said transfer. The machine only has 512+256 minus some megs stolen by built-in VGA of memory. The following is manually transcribed because crashdumps do not work[1], so there may be typos: panic: solaris assert: arc_buf_remove_buf(db->db_buf, db) =3D=3D 0,file: /usr/src/sys/modules/zfs/../../contrib/opensolaris/uts/common/fs/zfs/dbuf= =2Ec, line: 1718 cpuid =3D 0 KBD: enter: panic [thread pid 132 tid 100072] Stopped at kbd_enter+0x2b: nop db> bt Tracing pid 132 tid 100072 td 0xc3899d80 kbd_enter(c095f2c7) at kbd_enter+0x2b panic(c0c5ab69,c0c5b020,c0c5af8c,6b6,a99a,...) at pnic+0x11c dbuf_rele(cb874578,a99a,cb874578,a99a,0,...) at dbuf_rele+0x18c arc_write_done(c940b000,c940b200,c39aa000,c7663000,cbe93000,...) at arc_write_done+0x13a zio_done(c940b000,c0c3380f,c45fec00,0,1,...) at zio_done+0x1ee zio_vdev_io_assess(c940b000,c37bd104,c37bd124,c37bd148,929a53f1,...) at zio_vdev_io_assess+0x116 taskq_thread(c37bd0cc,ddb85d38) at taskq_thread+0x101 fork_exit(c0bfa2c4,c37bd0cc,ddb85d38) at fork_exit+0xac fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip =3D 0, esp =3D 0xddb85db70, ebp =3D 0 --- db> dmesg for the machine: http://distfiles.scode.org/mlref/freebsd-dmesg-zfs-panic-arcbufremove-7cu= rrent.txt It's a version of current compiled somewhere leading up to May 8. Contents of /boot/loader.conf: linux_load=3D"YES" geom_label_load=3D"YES" zfs_load=3D"YES" vm.kmem_size=3D272629760 Contents of /etc/sysctl.conf: kern.ps_arg_cache_limit=3D4096 kern.maxvnodes=3D15000 I have gotten this panic twice confirmed so far. The stacktrace is from the second instance. I did not grab the trace the first time because I was hoping for the crashdump. [1] Even after manually running "dumpon" and making sure it suceeded. Are crashdumps supposed to work on glabel devices? That is the only "special" circumstance I am aware of. --=20 / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schuller@infidyne.com>' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org --------------enig3B5F26B846054F8EFC18E4CA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGTFH1DNor2+l1i30RCOMyAJ4lMi3dlHfSmscYWM4wAAIdN2WXuwCg1tNC AkZPb3/Itlp5lDHQgEFnXvc= =LoVD -----END PGP SIGNATURE----- --------------enig3B5F26B846054F8EFC18E4CA--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?464C51EB.4050609>