Tom Lane wrote:
Yech. So much for RAID reliability ... maybe you need to reconfigure
the array for more redundancy?
Yeah...I'm not sure if I screwed the pooch by trying the bring the drive
back 'online'.in the past we just try re-seating it and the raid
card 'does its thing' and rebui
Jeff Amiel <[EMAIL PROTECTED]> writes:
> ran fsck
> PARTIALLY TRUNCATED INODE I=612353
> SALVAGE? yes
> INCORRECT BLOCK COUNT I=612353 (544 should be 416)
> CORRECT? yes
> [EMAIL PROTECTED] find /db -inum 612353
> /db/pg_clog/0952
Yech. So much for RAID reliability ... maybe you need to reconf
Wow. I just noticed I have the same problem today after a vacuum. As well as an
degraded array. Musta been a time release Y2k7 bug. Hopefully didn't loose
anything
too important.
Now that's room service! Choo
raid rebuilt...
ran fsck
PARTIALLY TRUNCATED INODE I=612353
SALVAGE? yes
INCORRECT BLOCK COUNT I=612353 (544 should be 416)
CORRECT? yes
PARTIALLY TRUNCATED INODE I=612389
SALVAGE? yes
INCORRECT BLOCK COUNT I=612389 (544 should be 416)
CORRECT? yes
INCORRECT BLOCK COUNT I=730298 (676448 should
