Date: Fri, 22 Sep 2006 15:03:29 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Vivek Khera <vivek@khera.org> Cc: stable@freebsd.org Subject: Re: ffs snapshot lockup Message-ID: <20060922190328.GA64849@xor.obsecurity.org> In-Reply-To: <917B087C-5E13-4D7F-94FA-95CB0E5C1884@khera.org> References: <917B087C-5E13-4D7F-94FA-95CB0E5C1884@khera.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060922190328.GA64849>