Date: Sun, 30 Apr 2006 17:15:50 +0400 (MSD) From: Dmitry Morozovsky <marck@rinet.ru> To: Kris Kennaway <kris@obsecurity.org> Cc: stable@freebsd.org Subject: Re: fsck_ufs locked in snaplk Message-ID: <20060430171414.X70630@woozle.rinet.ru> In-Reply-To: <20060429200327.R9621@woozle.rinet.ru> References: <20060423193208.N1187@woozle.rinet.ru> <20060423201732.GA74905@xor.obsecurity.org> <20060424091803.L20593@woozle.rinet.ru> <20060424215650.P36233@woozle.rinet.ru> <20060424181531.GA13774@xor.obsecurity.org> <20060425001751.S44618@woozle.rinet.ru> <20060424202859.GA18457@xor.obsecurity.org> <20060429200327.R9621@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 29 Apr 2006, Dmitry Morozovsky wrote: DM> KK> > I'll try to build DDB kernel tomorrow evening to check. Which commands should I DM> KK> > issue in ddb ? DM> KK> DM> KK> 'show lockedvnods', 'ps' and 'alltrace' are important. DM> DM> Well, common usage pattern does not lead to lock today. I made some DM> snapshots on quota'ed file system and delete them successfully. I finally can reproduce this: large rsync with mksnap_ffs in second or third run both locked in snaplk state. Debugging info available at http://woozle.net/FreeBSD/debug/office-ddb.20060430.txt.gz 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?20060430171414.X70630>