From owner-freebsd-current@FreeBSD.ORG Sat Dec 1 02:30:49 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4ECCF16A419; Sat, 1 Dec 2007 02:30:49 +0000 (UTC) (envelope-from peter@wemm.org) Received: from canning.wemm.org (canning.wemm.org [IPv6:2001:470:1f01:523::1]) by mx1.freebsd.org (Postfix) with ESMTP id 3527C13C44B; Sat, 1 Dec 2007 02:30:49 +0000 (UTC) (envelope-from peter@wemm.org) Received: from macbook.wemm.org (c-67-188-249-30.hsd1.ca.comcast.net [67.188.249.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: peter@canning.wemm.org) by canning.wemm.org (Postfix) with ESMTP id DC07646BA2; Fri, 30 Nov 2007 18:30:47 -0800 (PST) (envelope-from peter@wemm.org) Message-ID: <4750C750.2080307@wemm.org> Date: Fri, 30 Nov 2007 18:30:40 -0800 From: Peter Wemm User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Kostik Belousov References: <473B9A43.5060401@FreeBSD.org> <473CC522.5080904@FreeBSD.org> <20071116044858.GB78396@deviant.kiev.zoral.com.ua> <473D2516.9080805@samsco.org> <20071116051555.GC78396@deviant.kiev.zoral.com.ua> In-Reply-To: <20071116051555.GC78396@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ups@freebsd.org, tegge@freebsd.org, current@freebsd.org Subject: Re: panic: ffs_reallocblk: start == end X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Dec 2007 02:30:49 -0000 Kostik Belousov wrote: > On Thu, Nov 15, 2007 at 10:05:26PM -0700, Scott Long wrote: > >> Kostik Belousov wrote: >> >>> On Thu, Nov 15, 2007 at 11:16:02PM +0100, Kris Kennaway wrote: >>> >>>> Kris Kennaway wrote: >>>> >>>>> I got this panic on an 8 core amd64 running 8.0 when writing to a ufs on >>>>> a md device: >>>>> >>>>> panic: ffs_reallocblk: start == end >>>>> >>>>> db> wh >>>>> Tracing pid 59911 tid 100115 td 0xffffff0003b90000 >>>>> kdb_enter() at kdb_enter+0x31 >>>>> panic() at panic+0x1c0 >>>>> ffs_reallocblks() at ffs_reallocblks+0xb11 >>>>> VOP_REALLOCBLKS_APV() at VOP_REALLOCBLKS_APV+0xb9 >>>>> cluster_write() at cluster_write+0x38a >>>>> ffs_write() at ffs_write+0x575 >>>>> VOP_WRITE_APV() at VOP_WRITE_APV+0x147 >>>>> vn_write() at vn_write+0x213 >>>>> dofilewrite() at dofilewrite+0x9a >>>>> kern_writev() at kern_writev+0x4f >>>>> write() at write+0x4b >>>>> syscall() at syscall+0x301 >>>>> Xfast_syscall() at Xfast_syscall+0xab >>>>> --- syscall (4, FreeBSD ELF64, write), rip = 0x800a65d0c, rsp = >>>>> 0x7fffffffd268, rbp = 0x2800 --- >>>>> >>>>> Kris >>>>> >>>>> >>>> Another one of these on a different machine. Looks like something is >>>> definitely broken. >>>> >>>> >>> Kris, >>> this is consequence of the checks moved from DIAGNOSTIC to INVARIANTS >>> ifdef for ffs, and actually being compiled as result. Peter Holm reported >>> the "ffs_truncate3" panic. >>> >> So does this check identify a real problem that needs to be fixed? >> > > I believe so for ffs_truncate3. It seems that vtruncbuf sometime skips the > indirect blocks when cleaning buffer queues (at least when truncating to > zero length). > Hmm. Well, can we fix the reallocblks one then? My dev workstation at home is dying 1-2 times a day with "panic: ffs_reallocblks: start == end". Cheers, -Peter