Colleagues, one of my servers had to be rebooted uncleanly and then I have backgrounded fsck locked for more than an our in snaplk: 742 root 1 -4 4 1320K 688K snaplk 0:02 0.00% fsck_ufs File system in question is 200G gmirror on SATA. Usually making a snapshot (e.g., for making dumps) consumes 3-4 minutes for that fs, so it seems to me that filesystem is in a deadlock. Any hints? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------
On Sun, Apr 23, 2006 at 07:35:37PM +0400, Dmitry Morozovsky wrote:> Colleagues, > > one of my servers had to be rebooted uncleanly and then I have backgrounded > fsck locked for more than an our in snaplk: > > 742 root 1 -4 4 1320K 688K snaplk 0:02 0.00% fsck_ufs > > File system in question is 200G gmirror on SATA. Usually making a snapshot > (e.g., for making dumps) consumes 3-4 minutes for that fs, so it seems to me > that filesystem is in a deadlock.Is the process performing I/O? Background fsck deliberately runs at a slow rate so it does not destroy I/O performance on the rest of the system. Kris -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060423/8b9cba2b/attachment.pgp