From owner-freebsd-current@FreeBSD.ORG Tue Sep 28 19:58:43 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6F3E106566B for ; Tue, 28 Sep 2010 19:58:43 +0000 (UTC) (envelope-from takawata@init-main.com) Received: from sana.init-main.com (unknown [IPv6:2001:240:28::1]) by mx1.freebsd.org (Postfix) with ESMTP id F1A3E8FC1A for ; Tue, 28 Sep 2010 19:58:42 +0000 (UTC) Received: from ns.init-main.com (localhost [127.0.0.1]) by sana.init-main.com (8.14.3/8.14.3) with ESMTP id o8SJu1kr042376 for ; Wed, 29 Sep 2010 04:56:02 +0900 (JST) (envelope-from takawata@ns.init-main.com) Message-Id: <201009281956.o8SJu1kr042376@sana.init-main.com> To: freebsd-current@freebsd.org Date: Wed, 29 Sep 2010 04:56:01 +0900 From: Takanori Watanabe Subject: UFS related panic at night. 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: Tue, 28 Sep 2010 19:58:43 -0000 I happend to encountered panic related to UFS. It is occured by find(1) from daily script by NULL pointing sx(9) lock from UFS dirhash. Mounted filesystem is like this. %mount /dev/ada0s2a on / (ufs, local, soft-updates) devfs on /dev (devfs, local, multilabel) /dev/ada0s2e on /usr (ufs, NFS exported, local, soft-updates) /dev/ada0s2d on /var (ufs, local, soft-updates) procfs on /proc (procfs, local) And stack backtrace is at http://www.init-main.com/DVC00052.JPG (screen shot.)