Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 7C6806332E6 for ; Tue, 30 Mar 2010 07:16:45 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 62357-10 for ; Tue, 30 Mar 2010 10:16:33 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from ian.brad.office.comodo.net (brad.comodogroup.com [82.109.38.202]) by mail.postgresql.org (Postfix) with ESMTP id 7459E633130 for ; Tue, 30 Mar 2010 07:16:33 -0300 (ADT) Received: (qmail 11276 invoked by uid 1000); 30 Mar 2010 10:16:29 -0000 Received: from mahdell.brad.office.comodo.net (HELO mahdell.brad.office.comodo.net) (192.168.0.228) by ian.brad.office.comodo.net (qpsmtpd/0.40) with (AES256-SHA encrypted) ESMTPS; Tue, 30 Mar 2010 11:16:29 +0100 From: Mike Williams Organization: Comodo To: Alex Hunsaker Subject: Re: ERROR: could not open segment 1 of relation 1663/743352/743420 (target block 6407642): No such file or directory Date: Tue, 30 Mar 2010 10:16:28 +0000 User-Agent: KMail/1.9.10 Cc: Tom Lane , pgsql-admin@postgresql.org References: <201003281841.41865.mike.williams@comodo.com> <719e433b1c118d4d8de72f171199678a.squirrel@mail.brad.office.comodo.net> <34d269d41003291226n4bdc8f57t96132a22df64dea1@mail.gmail.com> In-Reply-To: <34d269d41003291226n4bdc8f57t96132a22df64dea1@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201003301116.28805.mike.williams@comodo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201003/237 X-Sequence-Number: 34036 On Monday 29 March 2010 20:26:08 Alex Hunsaker wrote: > > Test are para-virt VMs with "regular" kernels, production are real > > machines with hardened kernels (grsec+pax). > > Ive seen this error on a few boxes around here, using a non grsec > kernel fixes it. I never bothered to report it because I cant > reproduce it and it goes away without grsec. (2.6.30-32 IIRC, have > not tired the latest 33). Interestingly I have the *exact* same > hardware and setup (kernel/userspace/postgres etc) on a test machine > that I've never been able to trigger it on. Thanks Alex, good to know I've not screwed up the kernel somehow. I've been using 2.6.32 with grsecurity-2.1.14-2.6.32.9-201002231820 applied. -- Mike Williams