Tom Lane wrote:
> I concur it's too regular to be a hardware issue. The VMware idea is
> a bit plausible though. If that's it, we ought to see failures of this
> ilk on all four animals sooner or later ...
I've run full disk scans in both Windows VMs, and forced an fsck of the
host just to be on
Dave Page <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Is this the same physical machine as narwhal?
> Yes, it is. It's an FC6 box running VMWare server, with a Win 2k3r2 VM
> and a Vista ultimate VM, both with mingw and msvc animals.
> I'm still not convinced it's a hardware problem - aside
Tom Lane wrote:
> Dave Page <[EMAIL PROTECTED]> writes:
>> I've been seeing this failure intermittently on Narwhal HEAD, and once
>> on 8.1. Other branches have been OK, as have other animals running on
>> the same physical box. Narwhal-HEAD is run more often than any other
>> builds however.
>
>
Dave Page <[EMAIL PROTECTED]> writes:
> I've been seeing this failure intermittently on Narwhal HEAD, and once
> on 8.1. Other branches have been OK, as have other animals running on
> the same physical box. Narwhal-HEAD is run more often than any other
> builds however.
Oh, this is interesting:
This was another occurance of the strange create index failure on
Narwhal - unfortunately, despite having 'keep_error_builds' => 1 in my
BF config it seems to have removed the tree so I can't get the dump that
Tom wanted.
Does anyone know why the keep_error_builds option didn't work in this
case?
Dave Page wrote:
If you want to poke at it, I'd suggest changing the ERROR to PANIC
(it's in bufmgr.c) to cause a core dump, run installchecks till you
get a panic, and then look around in the dump to see what you can find.
Well, in typical fashion after 25+ runs this morning there's not a
fa
Dave Page <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I was afraid of that. Well, at least get a dump of page 104 in that
>> index so we can see what's on-disk.
> Sure - I'll have to try with 8.1/8.2 unless you have a pg_filedump
> that'll work with -HEAD?
No, I don't, but a plain hex/asci
Tom Lane wrote:
Dave Page <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
If you want to poke at it, I'd suggest changing the ERROR to PANIC
(it's in bufmgr.c) to cause a core dump, run installchecks till you
get a panic, and then look around in the dump to see what you can find.
It'd be particular
Dave Page <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> If you want to poke at it, I'd suggest changing the ERROR to PANIC
>> (it's in bufmgr.c) to cause a core dump, run installchecks till you
>> get a panic, and then look around in the dump to see what you can find.
>> It'd be particularly int
Tom Lane wrote:
> Dave Page <[EMAIL PROTECTED]> writes:
>> I've been seeing this failure intermittently on Narwhal HEAD, and once
>> on 8.1. Other branches have been OK, as have other animals running on
>> the same physical box. Narwhal-HEAD is run more often than any other
>> builds however.
>
>>
Dave Page <[EMAIL PROTECTED]> writes:
> I've been seeing this failure intermittently on Narwhal HEAD, and once
> on 8.1. Other branches have been OK, as have other animals running on
> the same physical box. Narwhal-HEAD is run more often than any other
> builds however.
> Anyone have any idea wha
I've been seeing this failure intermittently on Narwhal HEAD, and once
on 8.1. Other branches have been OK, as have other animals running on
the same physical box. Narwhal-HEAD is run more often than any other
builds however.
Anyone have any idea what might be wrong? It seems unlikely to be a
hard
12 matches
Mail list logo
