From owner-freebsd-stable@FreeBSD.ORG Fri Sep 22 18:55:38 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C91BB16A407 for ; Fri, 22 Sep 2006 18:55:38 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A91143D70 for ; Fri, 22 Sep 2006 18:55:35 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 177A3B810 for ; Fri, 22 Sep 2006 14:55:35 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v752.2) To: stable@freebsd.org Message-Id: <917B087C-5E13-4D7F-94FA-95CB0E5C1884@khera.org> Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-2-255508058; protocol="application/pkcs7-signature" From: Vivek Khera Date: Fri, 22 Sep 2006 14:55:34 -0400 X-Mailer: Apple Mail (2.752.2) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: ffs snapshot lockup X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Sep 2006 18:55:38 -0000 --Apple-Mail-2-255508058 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Yesterday we upgraded an amd64 system from 6.1 to 6.2-PRE from a cvsup of September 20 evening. The overnight nightly dump to tape went off normally. This afternoon when the sysadmin was performing the level0 backup, the ffs_mksnap program locked up the entire system. It wasn't the expected short hiccup that mksnap sometimes causes -- it was started just prior to lunchtime and when we got back everyone had wedged login sessions and IMAP sessions, and ffs_mksnap was in "D" state according to ps and idle for about 90 minutes. The only way out was to reboot the system. I know this is very un-useful as a bug report, but I'm putting this out in case anyone else has noticed this. It has never happened to us before when we were running 5.4 and then 6.1 on this box. Nothing else changed on the system during this time. The disk in question is on an adaptec RAID controller with the aac driver. --Apple-Mail-2-255508058--