From owner-freebsd-questions@FreeBSD.ORG Wed Aug 22 14:35:47 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D97116A418 for ; Wed, 22 Aug 2007 14:35:47 +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 2B43713C442 for ; Wed, 22 Aug 2007 14:35:47 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from rot26.obsecurity.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 7C9511A3C1A; Wed, 22 Aug 2007 07:33:49 -0700 (PDT) Received: by rot26.obsecurity.org (Postfix, from userid 1001) id 87789C3EE; Wed, 22 Aug 2007 10:35:46 -0400 (EDT) Date: Wed, 22 Aug 2007 10:35:46 -0400 From: Kris Kennaway To: Chris Morris Message-ID: <20070822143546.GA11446@rot26.obsecurity.org> References: <46CC41BF.4000203@sixfeetup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46CC41BF.4000203@sixfeetup.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-questions@freebsd.org Subject: Re: Snapshots fail on busy filesystem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 14:35:47 -0000 On Wed, Aug 22, 2007 at 10:01:35AM -0400, Chris Morris wrote: > Greetings to all, > > I'm trying to set up an automated system wherein snapshots of the file > system are taken prior to a backup run. The problem I'm running into > can best be described by the following bug report: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=100365&cat= > > I get this same problem completely at random, and thus is most likely > caused by the busy file system, I just don't have anything in place to > prove it as the bug submitter does. > > Has this bug ever been *really* fixed? The bug report seems to try to > call it fixed. I even contacted the bug reporter about this and he > admitted that the bug had never been fixed, but that he'd moved on and > never found a way around this. Sounds like you both need to talk to kib@. Of course as long as he thinks the problem is fixed he is not going to work on fixing it :) Kris