X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 0F319DB90A for ; Wed, 16 Nov 2005 14:25:41 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 44357-10 for ; Wed, 16 Nov 2005 18:25:40 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from cliff.cs.toronto.edu (cliff.cs.toronto.edu [128.100.3.120]) by svr1.postgresql.org (Postfix) with ESMTP id 4F664DB907 for ; Wed, 16 Nov 2005 14:25:38 -0400 (AST) Received: from eon.cs (eon.cs.toronto.edu [128.100.3.15]) by cliff.cs.toronto.edu (Postfix) with ESMTP id 1E1D25FD03; Wed, 16 Nov 2005 13:25:36 -0500 (EST) Received: by eon.cs (Postfix, from userid 1300) id 525DF7F4; Wed, 16 Nov 2005 13:25:36 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by eon.cs (Postfix) with ESMTP id 475C3544; Wed, 16 Nov 2005 13:25:36 -0500 (EST) Date: Wed, 16 Nov 2005 13:25:36 -0500 (EST) From: Qingqing Zhou X-X-Sender: zhouqq@eon.cs To: Kevin Grittner Cc: tgl@sss.pgh.pa.us, icub3d@gmail.com, pgsql-admin@postgresql.org Subject: Re: ERROR: could not read block In-Reply-To: <437B21E90200002500000781@gwmta.wicourts.gov> Message-ID: References: <437B21E90200002500000781@gwmta.wicourts.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.359 required=5 tests=[AWL=-0.120, DNS_FROM_RFC_ABUSE=0.479] X-Spam-Score: 0.359 X-Spam-Level: X-Archive-Number: 200511/214 X-Sequence-Number: 19587 On Wed, 16 Nov 2005, Kevin Grittner wrote: > Ran with this change. Didn't take long to hit it. > > [2005-11-16 11:59:29.015 ] 4904 LOG: > read failed on relation 1663/16385/1494810: -1 bytes, 1450 > [2005-11-16 11:59:29.015 ] 4904 ERROR: > could not read block 25447 of relation 1663/16385/1494810: Invalid > argument > 1450 ERROR_NO_SYSTEM_RESOURCES Insufficient system resources exist to complete the requested service SQL Server 7.0 experienced the same problem before: http://support.microsoft.com/default.aspx?scid=kb;en-us;274310 Some registration value tweak to solve it (for backup service): http://support.microsoft.com/default.aspx?scid=kb;en-us;304101 I have to go out for a while ... Kevin, can you take a look at the 2nd thread to see if it is possible to change some reg values to temporarily solve the problem. A more robust solution will follow a retry style following thread 1 I guess. Cheers, Qingqing