From owner-freebsd-stable@FreeBSD.ORG Sun Apr 23 20:17:34 2006 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 761C816A406 for ; Sun, 23 Apr 2006 20:17:34 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id B54B943D4C for ; Sun, 23 Apr 2006 20:17:33 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 990C51A3C29; Sun, 23 Apr 2006 13:17:33 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E46745564E; Sun, 23 Apr 2006 16:17:32 -0400 (EDT) Date: Sun, 23 Apr 2006 16:17:32 -0400 From: Kris Kennaway To: Dmitry Morozovsky Message-ID: <20060423201732.GA74905@xor.obsecurity.org> References: <20060423193208.N1187@woozle.rinet.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Nq2Wo0NMKNjxTN9z" Content-Disposition: inline In-Reply-To: <20060423193208.N1187@woozle.rinet.ru> User-Agent: Mutt/1.4.2.1i Cc: stable@FreeBSD.org Subject: Re: fsck_ufs locked in snaplk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Apr 2006 20:17:34 -0000 --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--