Data corruption

Hi all,

We have a database installed on Intel Xeon (Dell) and running on postgreSQL 8.1.
And the database couldn't start. Here is the logfile of what happend:

2006-11-14 00:28:38 PANIC: could not write to log file 6, segment 239 at offset 6430720, length 16384: Permission denied

2006-11-14 00:28:38 CONTEXT: writing block 557 of relation 1663/16403/985708

2006-11-14 00:28:38 STATEMENT: VACUUM client

abnormal program termination

2006-11-14 00:28:38 LOG: server process (PID 2868) was terminated by signal 3

2006-11-14 00:28:38 LOG: terminating any other active server processes

2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process

2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.

2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process

2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.

2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process

2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.

2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process

2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.

2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process

2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.

2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process

2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.

2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process

2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.

2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process

2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.

2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process

2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.

2006-11-14 00:28:38 WARNING: terminating connection because of crash of another server process

2006-11-14 00:28:38 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

2006-11-14 00:28:38 HINT: In a moment you should be able to reconnect to the database and repeat your command.

2006-11-14 00:28:38 LOG: all server processes terminated; reinitializing

2006-11-14 00:28:38 LOG: database system was interrupted at 2006-11-14 00:17:21 Eastern Standard Time

2006-11-14 00:28:38 LOG: checkpoint record is at 6/EEE1ED60

2006-11-14 00:28:38 LOG: redo record is at 6/EEE1ED60; undo record is at 0/0; shutdown FALSE

2006-11-14 00:28:38 LOG: next transaction ID: 13802854; next OID: 4807439

2006-11-14 00:28:38 LOG: next MultiXactId: 1; next MultiXactOffset: 0

2006-11-14 00:28:38 LOG: database system was not properly shut down; automatic recovery in progress

2006-11-14 00:28:38 LOG: redo starts at 6/EEE1EDA8

2006-11-14 00:28:40 LOG: could not read from log file 6, segment 239, offset 0: Permission denied

2006-11-14 00:28:40 LOG: redo done at 6/EEFFE740

2006-11-14 00:28:43 LOG: database system is ready

2006-11-14 00:28:43 LOG: transaction ID wrap limit is 2147484148, limited by database "postgres"

2006-11-14 01:50:58 LOG: could not receive data from client: No connection could be made because the target machine actively refused it.

2006-11-14 01:50:58 LOG: unexpected EOF on client connection

2006-11-14 01:51:18 ERROR: xlog flush request 6/EF5FB6B8 is not satisfied --- flushed only to 6/EEFFE7D0

2006-11-14 01:51:18 CONTEXT: writing block 21 of relation 1663/16403/2696

2006-11-14 01:51:19 ERROR: xlog flush request 6/EF5F8C50 is not satisfied --- flushed only to 6/EEFFE7D0

2006-11-14 01:51:19 CONTEXT: writing block 384 of relation 1663/16403/2619

Could someone tell us the cause of this. Or it's simply the command Vacuum client who caused all of this

Thanks