Date: Sun, 23 Apr 2006 16:17:32 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Dmitry Morozovsky <marck@rinet.ru> Cc: stable@FreeBSD.org Subject: Re: fsck_ufs locked in snaplk Message-ID: <20060423201732.GA74905@xor.obsecurity.org> In-Reply-To: <20060423193208.N1187@woozle.rinet.ru> References: <20060423193208.N1187@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--Nq2Wo0NMKNjxTN9z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 23, 2006 at 07:35:37PM +0400, Dmitry Morozovsky wrote: > Colleagues, >=20 > one of my servers had to be rebooted uncleanly and then I have background= ed=20 > fsck locked for more than an our in snaplk: >=20 > 742 root 1 -4 4 1320K 688K snaplk 0:02 0.00% fsck_ufs >=20 > File system in question is 200G gmirror on SATA. Usually making a snapsho= t=20 > (e.g., for making dumps) consumes 3-4 minutes for that fs, so it seems to= me=20 > 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 --Nq2Wo0NMKNjxTN9z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFES+DcWry0BWjoQKURAq0FAKCTjjTerD+Y5GfRa7V9M9w0F6+aVwCg6qz8 fgtmYX8SNME2jN+MKp0LSfo= =Djk5 -----END PGP SIGNATURE----- --Nq2Wo0NMKNjxTN9z--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060423201732.GA74905>