On Mon, Jul 7, 2008 at 2:08 PM, Andrew Hammond
<[EMAIL PROTECTED]> wrote:
> On Mon, Jul 7, 2008 at 12:33 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>> Also, I suggest filing a bug with your kernel distributor --- ENOSPC was
>> a totally misleading error code here. Seems like EIO would be more
>> appr
On Mon, Jul 7, 2008 at 12:33 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Andrew Hammond" <[EMAIL PROTECTED]> writes:
>>> On Thu, Jul 3, 2008 at 3:47 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
Have you looked into the machine's kernel log to see if there is any
evidence of low-level distress (
"Andrew Hammond" <[EMAIL PROTECTED]> writes:
>> On Thu, Jul 3, 2008 at 3:47 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>>> Have you looked into the machine's kernel log to see if there is any
>>> evidence of low-level distress (hardware or filesystem level)?
> Jun 19 03:06:14 db1 kernel: mpt1: attemp
On Thu, Jul 3, 2008 at 10:57 PM, Andrew Hammond
<[EMAIL PROTECTED]> wrote:
> On Thu, Jul 3, 2008 at 3:47 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>> Have you looked into the machine's kernel log to see if there is any
>> evidence of low-level distress (hardware or filesystem level)? I'm
>> wonderin
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Have you looked into the machine's kernel log to see if there is any
> evidence of low-level distress (hardware or filesystem level)? I'm
> wondering if ENOSPC is being reported because it is the closest
> available errno code, but the real problem is some
On Thu, Jul 3, 2008 at 3:47 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Andrew Hammond" <[EMAIL PROTECTED]> writes:
>> On Thu, Jul 3, 2008 at 2:35 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>>> The whole thing is pretty mystifying, especially the ENOSPC write
>>> failure on what seems like it couldn't
"Andrew Hammond" <[EMAIL PROTECTED]> writes:
> On Thu, Jul 3, 2008 at 2:35 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>> The whole thing is pretty mystifying, especially the ENOSPC write
>> failure on what seems like it couldn't have been a full disk.
> Yes, I've passed along the task of explaining w
On Thu, Jul 3, 2008 at 2:35 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Andrew Hammond" <[EMAIL PROTECTED]> writes:
>> Does anyone else have any suggestions about what I can do to diagnose this?
>
> The whole thing is pretty mystifying, especially the ENOSPC write
> failure on what seems like it cou
"Andrew Hammond" <[EMAIL PROTECTED]> writes:
> Does anyone else have any suggestions about what I can do to diagnose this?
The whole thing is pretty mystifying, especially the ENOSPC write
failure on what seems like it couldn't have been a full disk.
> Jun 27 15:54:31 qadb2 postgres[92519]: [44-1
Does anyone else have any suggestions about what I can do to diagnose this?
Do I need to re-initdb or can I reasonably keep running with the existing db?
A
On Mon, Jun 30, 2008 at 7:20 PM, Andrew Hammond
<[EMAIL PROTECTED]> wrote:
> On Fri, Jun 27, 2008 at 8:14 PM, Tom Lane <[EMAIL PROTECTED]> w
On Fri, Jun 27, 2008 at 8:14 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Andrew Hammond" <[EMAIL PROTECTED]> writes:
>> (I thought this line was interesting)
>> Jun 27 15:54:31 qadb2 postgres[92519]: [44-1] PANIC: could not open
>> relation 1663/16386/679439393: No such file or directory
>
>> I goo
"Andrew Hammond" <[EMAIL PROTECTED]> writes:
> (I thought this line was interesting)
> Jun 27 15:54:31 qadb2 postgres[92519]: [44-1] PANIC: could not open
> relation 1663/16386/679439393: No such file or directory
> I googled to find out what the numbers 1663/16386/679439393 from the
> PANIC mess
On Wed, Jun 25, 2008 at 9:57 AM, Andrew Hammond
<[EMAIL PROTECTED]> wrote:
>
> On Wed, Jun 25, 2008 at 2:58 AM, Heikki Linnakangas <[EMAIL PROTECTED]> wrote:
>>
>> Andrew Hammond wrote:
>>>
>>> I found this error message in my log files repeatedly:
>>>
>>> Error: failed to re-find parent key in "le
On Wed, Jun 25, 2008 at 2:58 AM, Heikki Linnakangas <[EMAIL PROTECTED]>
wrote:
> Andrew Hammond wrote:
>
>> I found this error message in my log files repeatedly:
>>
>> Error: failed to re-find parent key in "ledgerdetail_2008_03_idx2" for
>> deletion target page 64767
>>
>> I though "hmm, that in
Andrew Hammond wrote:
I found this error message in my log files repeatedly:
Error: failed to re-find parent key in "ledgerdetail_2008_03_idx2" for
deletion target page 64767
I though "hmm, that index looks broken. I'd better re-create it." So, I
dropped the index and then tried to create a new
I found this error message in my log files repeatedly:
Error: failed to re-find parent key in "ledgerdetail_2008_03_idx2" for
deletion target page 64767
I though "hmm, that index looks broken. I'd better re-create it." So, I
dropped the index and then tried to create a new one to replace it. Whic
16 matches
Mail list logo
