From owner-freebsd-fs@FreeBSD.ORG Sat Mar 11 09:45:45 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9742316A41F for ; Sat, 11 Mar 2006 09:45:45 +0000 (GMT) (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 5523043D45 for ; Sat, 11 Mar 2006 09:45:45 +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 37B4A1A4D87; Sat, 11 Mar 2006 01:45:45 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 474B4515BE; Sat, 11 Mar 2006 04:45:44 -0500 (EST) Date: Sat, 11 Mar 2006 04:45:44 -0500 From: Kris Kennaway To: Eugene Message-ID: <20060311094543.GA43910@xor.obsecurity.org> References: <004c01c644e8$c05c8c70$1b12c055@genie> <20060311090532.GA43378@xor.obsecurity.org> <001e01c644ef$68a76070$1b12c055@genie> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline In-Reply-To: <001e01c644ef$68a76070$1b12c055@genie> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org, Kris Kennaway Subject: Re: Dump/snapshot problems X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Mar 2006 09:45:45 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 11, 2006 at 12:37:03PM +0300, Eugene wrote: > Hi! >=20 > ----- Original Message -----=20 > From: "Kris Kennaway" > To: "Eugene" > Cc: > Sent: Saturday, March 11, 2006 12:05 > Subject: Re: Dump/snapshot problems >=20 > >> 1) System hangs or at least not accessible over the network and has to= =20 > >> be > >> physically reset. Last message on console > >> Collecting pv entries -- suggest increasing PMAP_SHPGPERPRO? > >> maxproc limit exceeded by id(0), please see tuning(7) and login.conf(5) > >> Question: what exactly should I tune? > > > >The value of PMAP_SHPGPERPROC in your kernel config, and the maxproc > >limit as described in those two manpages. >=20 > Well, I can read -) I would like to know why it fails in virtually unload= ed=20 > system (except for dump) and what parameters/values _in particular_ shoul= d=20 > be tweaked. See the NOTES file for discussion of the former, and please read the manpages. > >You can ignore the fsync message, it's a side-effect of the snapshot > >operation not succeeding. Just retry the dump. >=20 > That's very comforting but why is it not succeding? And I would really li= ke=20 > the dump to work automatically (as it did for more than a year before the= se=20 > problems started to appear recently). I don't know. Kris --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEEpxHWry0BWjoQKURArO1AKD9EBOb+OhnRFnc+UOnV+n5H8HKQACg8rRV Eq4bRt3qPaQs1Z4SaJ2bcrs= =O4x1 -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM--