Date: Mon, 14 Jun 2004 13:10:11 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: Ronald Klop <ronald-freebsd7@klop.yi.org> Cc: FreeBSD-current <freebsd-current@freebsd.org> Subject: Re: panic: ffs_valloc: dup alloc Message-ID: <Pine.NEB.3.96L.1040614130818.34947A-100000@fledge.watson.org> In-Reply-To: <opr9lgi9yam97yfk@outgoing.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 14 Jun 2004, Ronald Klop wrote: > I'm getting this panic 'panic: ffs_valloc: dup alloc'. It happens on > -CURRENT, since quite some time. It happens when doing an rsync from a > remote server to my secondary disk. (ad2,master on ata1), there is no > slave on this controller. And it always happens, so it is very > repeatable. Is this probably a hardware failure? Or software? "dup alloc" tends to be a common symptom of races or other corruption (improper zeroing of memory, etc). One thing I might recommend doing, if you haven't done it already, is to boot to single-user and do a manual fsck of the drive experiencing the problem to help identify if on-disk corruption is the source. It might well be useful to log the results of that fsck to a log file (perhaps in an md memory backed file system) to include in a follow-up if there's anything interesting. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research > > $ uname -a > FreeBSD henk.thuis.klop.ws 5.2-CURRENT FreeBSD 5.2-CURRENT #24: Mon Jun 14 > 00:25:19 CEST 2004 root@henk.thuis.klop.ws:/usr/obj/usr/src/sys/HENK > i386 > > A backtrace of the kernel core dump is in the attached gdb.txt. > My dmesg is also attached. > > Can I provide more info? > > Greetings, > > Ronald. > > PS: Searched the archives and google, but didn't find anything usefull yet. > > -- > Ronald Klop > Amsterdam, The Netherlands >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1040614130818.34947A-100000>