From owner-freebsd-questions@FreeBSD.ORG Mon Dec 5 15:55:14 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E91916A41F for ; Mon, 5 Dec 2005 15:55:14 +0000 (GMT) (envelope-from w@expro.pl) Received: from miranda.expro.pl (miranda.expro.pl [193.25.166.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1555143D90 for ; Mon, 5 Dec 2005 15:54:58 +0000 (GMT) (envelope-from w@expro.pl) Received: by miranda.expro.pl (Postfix, from userid 1001) id 80B0954871; Mon, 5 Dec 2005 16:54:53 +0100 (CET) Date: Mon, 5 Dec 2005 16:54:53 +0100 From: Jan Srzednicki To: freebsd-questions@freebsd.org Message-ID: <20051205155453.GB24388@miranda.expro.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i Subject: A snapshot-related FFS panic and a Mylex RAID question X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 15:55:14 -0000 Hi, I'm running FreeBSD 5.4-R with the official maintenance patches. I've recently encountered the following issue while doing 'dump -L' of an partition: kernel: panic: snapacct_ufs2: bad block That's pretty all I've got, because my Mylex controller doesn't want to be a dump device: [16:51] hostname:~ # dumpon -v /dev/mlxd0s1b dumpon: ioctl(DIOCSKERNELDUMP): Operation not supported by device Google is silent on that topic. So here are my questions: 1) Are there any chances the mentioned FFS problem has been fixed in 6.0 or the incoming 5.5-R? If yes, can I backport the fixes? 2) Can Mylex be somehow forced to accept the dump? What's the reason it doesn't support it? greetings, -- Jan Srzednicki w@expro.pl