amd64/124432: 7.0-STABLE panic: invalbuf: dirty bufs
Joe Kelsey
joe at zircon.seattle.wa.us
Mon Jun 9 22:50:04 UTC 2008
>Number: 124432
>Category: amd64
>Synopsis: 7.0-STABLE panic: invalbuf: dirty bufs
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-amd64
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Jun 09 22:50:04 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: Joe Kelsey
>Release: FreeBSD 7.0-STABLE amd64
>Organization:
Joseph M. Kelsey
>Environment:
System: FreeBSD zircon.zircon.seattle.wa.us 7.0-STABLE FreeBSD 7.0-STABLE #18: Sun May 25 15:43:06 PDT 2008 root at zircon.zircon.seattle.wa.us:/usr/obj/usr/src/sys/ZIRCON amd64
>Description:
Kernel panic: invalbuf: dirty bufs
Seems to happen under moderate disk activity. It happened twice
so far during my attempt to move several directories from one
disk to another. I do not see any real issue with the disk
traffic, except that I am moving from a gmirror device to a
normal device, on different ata attach points. The gmirror is
on a fast SATA (300) interface and the other device is on a
slower (150) SATA interface. I have 4 SATA interfaces on this
system, the two standard ata interfaces on the mother board and
two SATA interfaces to attach my real SATA disks. So, the
gmirror gets the fast one and everyone else gets the slower one.
I have vmcore if it is of interest to anyone.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-amd64
mailing list