Date: Tue, 25 Apr 2006 00:25:37 +0400 (MSD) From: Dmitry Morozovsky <marck@rinet.ru> To: Michael Butler <imb@protected-networks.net> Cc: stable@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: fsck_ufs locked in snaplk Message-ID: <20060425002421.W44618@woozle.rinet.ru> In-Reply-To: <444D1648.4040100@protected-networks.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 *** ------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060425002421.W44618>