[prev in list] [next in list] [prev in thread] [next in thread]
List: postgresql-admin
Subject: Re: [ADMIN] ERROR: could not read block
From: Diego_Fernández_Slezak <dfslezak () gmail ! com>
Date: 2011-05-22 22:24:26
Message-ID: BANLkTikpCjYmmjHK30RTrsL1yZH8RbmAiw () mail ! gmail ! com
[Download RAW message or body]
Thanks Tom.
I executed a REINDEX DATABASE and received the error:
.
.
.
NOTICE: table "pg_enum" was reindexed
NOTICE: table "pg_namespace" was reindexed
NOTICE: table "pg_conversion" was reindexed
NOTICE: table "pg_depend" was reindexed
NOTICE: table "users" was reindexed
NOTICE: table "results" was reindexed
NOTICE: table "games" was reindexed
NOTICE: table "game_status" was reindexed
ERROR: could not extend relation 1663/350994/448678: wrote only 4096 of
8192 bytes at block 44030
HINT: Check free disk space.
When I check free space, I have more than 100GB free:
$ df -h
/dev/sdc1 917G 742G 130G 86% /home
Also, when I check what does this file correspond to I get a empty answer:
/usr/lib/postgresql/8.3/bin/oid2name -d mydb -f 448678
From database "mydb":
Filenode Table Name
----------------------
Thanks in advance
Diego
On Sat, May 21, 2011 at 12:16 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> =?ISO-8859-1?Q?Diego_Fern=E1ndez_Slezak?= <dfslezak@gmail.com> writes:
> > Hello everybody,
> > I had a hard drive failure last week. After lots of effort I've been able
> to
> > backup a 700GB database, with only one file with corruption.
>
> > When I do some big queries, it throws me errors on this faulty file:
> > could not read block 390041 of relation 1663/350994/351212: read only 0
> of
> > 8192 bytes
>
> I'm guessing this is the result of an index entry pointing to a block
> that's not there --- either the index is corrupted, or you lost some
> data. In any case, reindexing the table ought to get rid of this error.
>
> regards, tom lane
>
[Attachment #3 (text/html)]
Thanks Tom.<br>I executed a REINDEX DATABASE and received the \
error:<br><br>.<br>.<br>.<br>NOTICE: table "pg_enum" was \
reindexed<br>NOTICE: table "pg_namespace" was reindexed<br>NOTICE: table \
"pg_conversion" was reindexed<br>
NOTICE: table "pg_depend" was reindexed<br>NOTICE: table \
"users" was reindexed<br>NOTICE: table "results" was \
reindexed<br>NOTICE: table "games" was reindexed<br>NOTICE: table \
"game_status" was reindexed<br>
ERROR: could not extend relation 1663/350994/448678: wrote only 4096 of 8192 bytes \
at block 44030<br>HINT: Check free disk space.<br><br>When I check free space, I \
have more than 100GB free:<br>$ df -h<br>/dev/sdc1 917G 742G 130G 86% \
/home<br>
<br>Also, when I check what does this file correspond to I get a empty \
answer:<br>/usr/lib/postgresql/8.3/bin/oid2name -d mydb -f 448678<br>From database \
"mydb":<br> Filenode Table Name<br>----------------------<br>
<br><br>Thanks in advance<br>Diego<br><br><div class="gmail_quote">On Sat, May 21, \
2011 at 12:16 PM, Tom Lane <span dir="ltr"><<a \
href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;">
<div class="im">=?ISO-8859-1?Q?Diego_Fern=E1ndez_Slezak?= <<a \
href="mailto:dfslezak@gmail.com">dfslezak@gmail.com</a>> writes:<br> > Hello \
everybody,<br> > I had a hard drive failure last week. After lots of effort \
I've been able to<br> > backup a 700GB database, with only one file with \
corruption.<br> <br>
> When I do some big queries, it throws me errors on this faulty file:<br>
> could not read block 390041 of relation 1663/350994/351212: read only 0 of<br>
> 8192 bytes<br>
<br>
</div>I'm guessing this is the result of an index entry pointing to a block<br>
that's not there --- either the index is corrupted, or you lost some<br>
data. In any case, reindexing the table ought to get rid of this error.<br>
<br>
regards, tom lane<br>
</blockquote></div><br>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic