SCSI Error

On Fri, 20 Sep 2002, Ricardo Fogliati wrote:

Hiya Lists....

Somebody could help me? I am with an error when the Postgresql makes Insert,
Delete or Update

kernel: SCSI disk error : host 2 channel 0 id 0 lun 0 return code = 70000
kernel: I/O error: dev 08:08, sector 47938856
kernel: SCSI disk error : host 2 channel 0 id 0 lun 0 return code = 70000
kernel: I/O error: dev 08:08, sector 47938800
kernel: SCSI disk error : host 2 channel 0 id 0 lun 0 return code = 70000
kernel: I/O error: dev 08:08, sector 47938864
kernel: SCSI disk error : host 2 channel 0 id 0 lun 0 return code = 70000
kernel: I/O error: dev 08:08, sector 47938872
kernel: SCSI disk error : host 2 channel 0 id 0 lun 0 return code = 70000
kernel: I/O error: dev 08:08, sector 47938808

Version:

postgresql-7.2.1-5
[deleted]...
Kernel:

Linux version 2.4.7-10custom (gcc version 2.96 20000731 (Red Hat Linux 7.1
2.96-98)) #9 Mon
Sep 16 17:50:13 BRT 2002

Not sure what you're asking for. That's a hardware error. Back up immediately,
if you haven't already got decent backups, and fix the disk/controller.

Could possibly be a filesystem error but even if so it's still casting doubt on
the hardware. On the other hand I do believe I saw a message recently saying
that some of the 2.4 series kernels had file system bugs. I don't know which,
someone else might be able to expand.

--
Nigel J. Andrews

On Fri, Sep 20, 2002 at 01:32:52PM +0100, Nigel J. Andrews wrote:

the hardware. On the other hand I do believe I saw a message
recently saying that some of the 2.4 series kernels had file system
bugs.

I recall problems, offhand, with 2.4.5, 2.4.10, 2.4.11 (which was so
broken that you couldn't recover), and 2.4.15. I seem to recall a
report on 2.4.12, also. There's a page at
<http://www.atnf.csiro.au/people/rgooch/linux/docs/kernel-newsflash.html&gt;
that provides some summaries of known problems, and filesystem
corruption doesn't show up for all the ones I mentioned, so maybe my
memory is faulty (alas, I didn't get the ECC option).

A

-- 
----
Andrew Sullivan                         204-4141 Yonge Street
Liberty RMS                           Toronto, Ontario Canada
<andrew@libertyrms.info>                              M2P 2A8
                                         +1 416 646 3304 x110

Ensure you don't have termination issues. Make sure your SCSI interface
is configured correctly for your SCSI environment, especially on matters
of termination. Make sure you have enough power to your drive and if
possible, make sure your drives are hung off of distinct power segments
coming from your power supply. Of course, make sure you have enough
power being supplied from your power supply to power all of your drives
and *equipment* (cards, CPU, fans, etc). Last, be sure your cables are
in good working order and that they are as far away from the power
supply and cables as is possible. SCSI is notorious for suffering from
RF interference especially on long cables. If all else fails, you may
try swapping cables to see if this helps.

If at all possible, immediately fsck (!!!!don't make it perform any
repairs!!!!) and backup! The fsck will let you know if you should
reasonably expect to have a meaningful backup. Requesting fsck to
repair in this situation could actually result in more/worse
(unrecoverable) corruption. If the fsck does report potential FS
damage, accept the fact that some of your data (and resulting backup)
may be corrupt, perhaps even unrecoverably so.

I'm using a 7880 here and have never had notable issues save only for
bugs in the Linux SCSI drivers.

Greg

the hardware. On the other hand I do believe I saw a message
recently saying that some of the 2.4 series kernels had file system
bugs.

I recall problems, offhand, with 2.4.5, 2.4.10, 2.4.11 (which was so
broken that you couldn't recover), and 2.4.15. I seem to recall a
report on 2.4.12, also. There's a page at
<http://www.atnf.csiro.au/people/rgooch/linux/docs/kernel-newsflash.html&gt;
that provides some summaries of known problems, and filesystem
corruption doesn't show up for all the ones I mentioned, so maybe my
memory is faulty (alas, I didn't get the ECC option).

Hehehe - those poor sad people who use Linux - try FreeBSD for a change, at
least it works ;)

Chris