From owner-freebsd-stable@FreeBSD.ORG Fri Sep 22 19:03:31 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 BD97A16A407 for ; Fri, 22 Sep 2006 19:03:31 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8954F43D46 for ; Fri, 22 Sep 2006 19:03:31 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id C92DA1A3C1F; Fri, 22 Sep 2006 12:03:30 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 3BAF3515F4; Fri, 22 Sep 2006 15:03:29 -0400 (EDT) Date: Fri, 22 Sep 2006 15:03:29 -0400 From: Kris Kennaway To: Vivek Khera Message-ID: <20060922190328.GA64849@xor.obsecurity.org> References: <917B087C-5E13-4D7F-94FA-95CB0E5C1884@khera.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <917B087C-5E13-4D7F-94FA-95CB0E5C1884@khera.org> User-Agent: Mutt/1.4.2.2i Cc: stable@freebsd.org Subject: Re: 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 19:03:31 -0000 On Fri, Sep 22, 2006 at 02:55:34PM -0400, Vivek Khera wrote: > 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. Yep, we'd need additional debugging to proceed. Kris