Re: panic: ffs_valloc: dup alloc

From: Ronald Klop (ronald-freebsd7_at_klop.yi.org)
Date: 06/16/04

  • Next message: Brian Feldman: "Re: ** HEADS UP ** GDB detached from the 5-CURRENT build" 
    Date: Wed, 16 Jun 2004 21:12:58 +0200
To: Robert Watson <rwatson@freebsd.org>

    On Mon, 14 Jun 2004 13:10:11 -0400 (EDT), Robert Watson
    <rwatson@freebsd.org> wrote:

    > 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.

    I reproduced the problem on a 'fsck -y' cleaned fs.
    Attached is the output of the (second) 'fsck -y' after the panic.

    Can you (or somebody else) take a look at it?

    Greetings,

    Ronald. 

    -- 
  Ronald Klop
  Amsterdam, The Netherlands

    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Brian Feldman: "Re: ** HEADS UP ** GDB detached from the 5-CURRENT build"

    Relevant Pages