From owner-freebsd-current@FreeBSD.ORG Thu Mar 23 18:34:19 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 629D716A424; Thu, 23 Mar 2006 18:34:19 +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 40AAE43DC0; Thu, 23 Mar 2006 18:34:15 +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 D4D241A4E87; Thu, 23 Mar 2006 10:34:14 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 365AB51753; Thu, 23 Mar 2006 13:34:14 -0500 (EST) Date: Thu, 23 Mar 2006 13:34:14 -0500 From: Kris Kennaway To: John Kozubik Message-ID: <20060323183414.GA84775@xor.obsecurity.org> References: <20060320224313.O55763@kozubik.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="45Z9DzgjV8m4Oswq" Content-Disposition: inline In-Reply-To: <20060320224313.O55763@kozubik.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org, jroberson@chesapeake.net, freebsd-current@freebsd.org, tegge@freebsd.org, kris@obsecurity.org Subject: Re: UFS2 Snapshots in 6.1-Beta4 - Confirmed Problems 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: Thu, 23 Mar 2006 18:34:19 -0000 --45Z9DzgjV8m4Oswq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Mar 21, 2006 at 01:36:44AM -0800, John Kozubik wrote: > First, I have confirmed that a filesystem with multiple snapshots that > undergoes multiple, rapid deletions of files, will cause the system to > hang. I have witnessed this before, but had not confirmed it or > documented it in a PR. Now that I have confirmed this behavior, I have > documented it in: kern/94769 I ran a (completion of) your script in a loop for about 24 hours and it didn't deadlock. This may be because there was a second set of fixes that was merged in to 6.x a day or two ago. Are you able to confirm whether they indeed fixed this problem? > Second, kern/92292 is still a problem. I have reproduced this error in > 6.1-BETA4 (and have seen it happening since 5.1). The (small) difference > is that the cp process seems to stick in the flswai state instead of > biowr. I'll test this one next. Kris --45Z9DzgjV8m4Oswq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEIuolWry0BWjoQKURAk5hAJwNxVVgMARq2Vuxr7j+WEaBgckiHgCg7a3S oR0bG21GB9Mg1bNFYlHM96M= =EUji -----END PGP SIGNATURE----- --45Z9DzgjV8m4Oswq--