pg_dumpall errors.

We recently had an unexpected san outage which caused
our postgresql to stop pg_dumpall'ing properly. As a
unix admin, not a db person, i'm short on ideas for
what I should try next.

some base info:
RHAS2.1 box

postgresql-libs-7.1.3-4bp.2
postgresql-jdbc-7.1.3-4bp.2
postgresql-tk-7.1.3-4bp.2
postgresql-7.1.3-4bp.2
postgresql-contrib-7.1.3-4bp.2
postgresql-perl-7.1.3-4bp.2
postgresql-docs-7.1.3-4bp.2
postgresql-python-7.1.3-4bp.2
postgresql-server-7.1.3-4bp.2
postgresql-tcl-7.1.3-4bp.2
postgresql-odbc-7.1.3-4bp.2

#pg_dumpall > pg_dumpall.txt
ERROR: not all toast chunks found for value 12660184
PQendcopy: resetting connection
SQL query to dump the contents of Table 'inmail_' did
not execute correctly. After we read all the table
contents from the backend, PQendcopy() failed.
Explanation from backend: ''.
The query was: 'COPY "inmail_" TO stdout;
'.
pg_dump failed on lmpg, exiting

#vacuumdb -z -v lmpg
NOTICE: --Relation pg_type--
NOTICE: Pages 3: Changed 0, reaped 0, Empty 0, New 0;
Tup 202: Vac 0, Keep/VTL 0/0, Crash 0, UnUsed 0,
MinLen 106, MaxLen 109; Re-using: Free/Avail. Space
0/0; EndEmpty/Avail. Pages 0/0. CPU 0.00s/0.00u sec.
....
....
NOTICE: --Relation pg_toast_18779--
NOTICE: Pages 3745: Changed 0, reaped 437, Empty 0,
New 0; Tup 16223: Vac 0, Keep/VTL 0/0, Crash 0, UnUsed
539, MinLen 46, MaxLen 2034; Re-using: Free/Avail.
Space 33756/31020; EndEmpty/Avail. Pages 0/64. CPU
0.09s/0.01u sec.
NOTICE: Index pg_toast_18779_idx: Pages 222; Tuples
16223: Deleted 0. CPU 0.02s/0.03u sec.
NOTICE: Rel pg_toast_18779: Pages: 3745 --> 3745;
Tuple(s) moved: 0. CPU 0.05s/0.01u sec.
NOTICE: Analyzing...
ERROR: not all toast chunks found for value 12660184
vacuumdb: vacuum lmpg failed

Thanks in advance,
and if anyone wants more info, please let me know...

Luke

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/