From owner-freebsd-stable@FreeBSD.ORG Mon Apr 24 20:25:39 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 CBD4216A402 for ; Mon, 24 Apr 2006 20:25:39 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CAD543D46 for ; Mon, 24 Apr 2006 20:25:38 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.6/8.13.4) with ESMTP id k3OKPblJ044717; Tue, 25 Apr 2006 00:25:38 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Tue, 25 Apr 2006 00:25:37 +0400 (MSD) From: Dmitry Morozovsky To: Michael Butler In-Reply-To: <444D1648.4040100@protected-networks.net> Message-ID: <20060425002421.W44618@woozle.rinet.ru> References: <20060423193208.N1187@woozle.rinet.ru> <20060423201732.GA74905@xor.obsecurity.org> <20060424091803.L20593@woozle.rinet.ru> <20060424215650.P36233@woozle.rinet.ru> <444D1648.4040100@protected-networks.net> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (woozle.rinet.ru [0.0.0.0]); Tue, 25 Apr 2006 00:25:38 +0400 (MSD) Cc: stable@freebsd.org, Kris Kennaway Subject: Re: fsck_ufs locked in snaplk 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: Mon, 24 Apr 2006 20:25:39 -0000 On Mon, 24 Apr 2006, Michael Butler wrote: MB> Dmitry Morozovsky wrote: MB> > one of my servers had to be rebooted uncleanly and then I have MB> > backgrounded fsck locked for more than an our in snaplk: MB> MB> Given that this system came down uncleanly, have you tried starting up in MB> single-user and manually doing an fsck (without '-p') on the afflicted MB> file-system? My guess is that there's something there which can't be MB> resolved automagically, Yes I did, and I'd completely disabled bgfsck. However, after it I got snapshot lock in nightly backup, and a second one on a manual test. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------