Date: Mon, 24 Apr 2006 09:24:10 +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: <20060424091803.L20593@woozle.rinet.ru> In-Reply-To: <20060423201732.GA74905@xor.obsecurity.org> References: <20060423193208.N1187@woozle.rinet.ru> <20060423201732.GA74905@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 23 Apr 2006, Kris Kennaway wrote: kKK> > one of my servers had to be rebooted uncleanly and then I have backgrounded KK> > fsck locked for more than an our in snaplk: KK> > KK> > 742 root 1 -4 4 1320K 688K snaplk 0:02 0.00% fsck_ufs KK> > KK> > File system in question is 200G gmirror on SATA. Usually making a snapshot KK> > (e.g., for making dumps) consumes 3-4 minutes for that fs, so it seems to me KK> > that filesystem is in a deadlock. KK> KK> Is the process performing I/O? Background fsck deliberately runs at a KK> slow rate so it does not destroy I/O performance on the rest of the KK> system. Nope. For that case, 50+ smbds had been locked in 'ufs' state, so I've been urged to revive the machine and reboot, turning off bgfsck. This night, dump -L locks in the same position on the same filesystem: 0 2887 2886 0 -4 0 1260 692 snaplk D ?? 0:01.28 /sbin/mksnap_ffs root 0.0 0.1 5:19AM it has been started at 5:19am, and now is 9:20 - no disk activity For the reference: it's fresh RELENG_6_1/i386. 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?20060424091803.L20593>