From owner-freebsd-current@FreeBSD.ORG Wed Feb 4 15:29:30 2004 Return-Path: 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 BF0C316A4CE; Wed, 4 Feb 2004 15:29:30 -0800 (PST) Received: from beastie.mckusick.com (beastie.mckusick.com [209.31.233.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id B634B43D4C; Wed, 4 Feb 2004 15:29:25 -0800 (PST) (envelope-from mckusick@beastie.mckusick.com) Received: from beastie.mckusick.com (localhost [127.0.0.1]) by beastie.mckusick.com (8.12.8/8.12.3) with ESMTP id i14NTOok054320; Wed, 4 Feb 2004 15:29:24 -0800 (PST) (envelope-from mckusick@beastie.mckusick.com) Message-Id: <200402042329.i14NTOok054320@beastie.mckusick.com> To: "Kenneth D. Merry" In-Reply-To: Your message of "Wed, 04 Feb 2004 15:56:57 MST." <20040204225657.GA55243@panzer.kdm.org> Date: Wed, 04 Feb 2004 15:29:24 -0800 From: Kirk McKusick X-Mailman-Approved-At: Thu, 05 Feb 2004 05:14:12 -0800 cc: current@FreeBSD.org Subject: Re: panic: softdep_move_dependencies: need merge code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 04 Feb 2004 23:29:30 -0000 Date: Wed, 4 Feb 2004 15:56:57 -0700 From: "Kenneth D. Merry" To: current@FreeBSD.org Cc: mckusick@mckusick.com Subject: panic: softdep_move_dependencies: need merge code X-ASK-Info: Whitelist match I ran into the following panic on a machine running -current from a week or two ago: panic("softdep_move_dependencies: need merge code"); (see softdep_move_dependencies() in ffs_softdep.c) When this happened, I had a filesystem mounted and I was writing to it when the underlying storage device crashed. Around the time the device came back up, I got the above panic. Does anyone have any clues about this one? Thanks, Ken -- Kenneth Merry ken@FreeBSD.ORG This panic can happen when an I/O fails (e.g., returns EIO) and the soft dependencies cannot be rolled back. Actually, they could be rolled back, but the only time that this can occur is in the face of an unrecoverable error from the storage media, so I did not bother to write the (considerable amount of) code to do the rollback. Kirk McKusick