Date: 02 May 2003 15:22:12 -0400 From: Joe Marcus Clarke <marcus@marcuscom.com> To: current@freebsd.org Subject: More on the blkfree panic Message-ID: <1051903332.568.37.camel@gyros>
next in thread | raw e-mail | index | archive | help
--=-hHI7H52VTydVohJ1UnP9 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable This panic started happening to me after I cvsup'd and rebuilt yesterday. Prior to that I never had the problem with a -CURRENT from 04/26 (using the same steps listed below). Now I can reliably reproduce the crash on: FreeBSD bulgogi.cisco.com 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Fri May 2 14:08:06 EDT 2003 =20 marcus@bulgogi.cisco.com:/usr/obj/usr/src/sys/BULGOGI i386 All my file systems are UFS2 with softupdates. The way I reproduce this, is I have the following: /dev/ad0s1f 34G 3.0G 28G 10% /space On /space, I have a current ports tree in ports/. I have /space NFS-exported with /space/ports as an allowed mount point. I then mount /space/ports to /space/jails/current/a/ports on the same machine: mount -o nfsv3,intr -r localhost:/space/ports /space/jails/current/a/ports Then, I run: chroot /space/jails/current (cd /usr/ports/x11/gnome2; make checksum-recursive) A few seconds later, the system crashes with the same backtrace that has previously been sent to the list. Running a full fsck from single-user did not help. Joe --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-hHI7H52VTydVohJ1UnP9 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQA+ssVkb2iPiv4Uz4cRAp67AJ4ilWlMSPXkW1/BYeaov/k3tTkqvwCfRFYE MkowInGOIRmFY3al2ghogzs= =s47o -----END PGP SIGNATURE----- --=-hHI7H52VTydVohJ1UnP9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1051903332.568.37.camel>