From owner-freebsd-current Tue Feb 4 0:24:31 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF9A337B401; Tue, 4 Feb 2003 00:24:29 -0800 (PST) Received: from mail.rpi.edu (mail.rpi.edu [128.113.2.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1052243E4A; Tue, 4 Feb 2003 00:24:29 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id h148OIGB224328; Tue, 4 Feb 2003 03:24:18 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Tue, 4 Feb 2003 03:24:16 -0500 To: current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Panic#2 copying many files from UFS to UFS2 partition Cc: kirk@mckusick.com, Poul-Henning Kamp Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 7:50 PM -0500 1/29/03, Garance A Drosihn wrote: >At 9:49 PM -0500 1/28/03, Garance A Drosihn wrote: >>Hmm, well, I finally got my first actual system panic which wasn't >>obviously caused by my own screwing around. On the console I have: >> >> free inode /usr/cvs/net/64 had 0 blocks >> panic: Negative bio_offset (-19038208) on bio 0xce51be28 >> cpuid = 0; lapic.id = 01000000 >> Debugger("panic") >> Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0 > >It looks like the sequence which generated that panic can be >repeated to generate other panics. My sequence was: > > use sysinstall to remove and then recreate the > new UFS2 partition, 3100 meg in size, > mounted on /usr/cvs/net > pushd /usr/cvs/net-old > tar cf - ./ | (popd; cd /usr/cvs/net; tar xpf -) > >and again I got a panic, although not quite the same panic. >It also seemed like it happened much sooner in the process. >So, what should I do at this point to help pin this down? To follow up on this... After cvsup-ing to the 5.0-current from Feb 3rd, I can not reproduce the panic. Apparently the problem was something that was fixed in the past week or so. There is probably no need to look into these two panic reports. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message