journal commit I/O error

[Vito Corleone]

Hi,
I am running Debian Sarge with kernel 2.6.6. The server is mainly used for DB server, never had problem like this before. Suddenly this morning I got this message:
Message from syslogd@localhost at Mon Jul 19 09:16:43 2004 ...
localhost kernel: journal commit I/O error

And when I tried to ls, I got this error:
-bash: /bin/ls: Input/output error

What happened? How do I fix this? Please help.

Regards.
Vito

[Michael Buchenrieder]

Vito Corleone <corl...@godfather.com> writes:

>Hi,
>I am running Debian Sarge with kernel 2.6.6. The server is mainly used for DB server,

Yuck.

>never had problem like this before. Suddenly this morning I got this message:
>Message from syslogd@localhost at Mon Jul 19 09:16:43 2004 ...
>localhost kernel: journal commit I/O error

>And when I tried to ls, I got this error:
>-bash: /bin/ls: Input/output error

Bad. Very bad.

>What happened? How do I fix this? Please help.

[...]

If you're lucky, it's just a memory problem, but I fear that
you have probably have a bad HD (the kernel error would indicate
a problem with the filesystem used; possibly ext3).

Try rebooting the machine, and check the error log. If even a simple
/bin/ls doesn't work, then something is seriously damaged, but without
a correctly running system, you won't get very far at this point for
any kind of diagnosis while it is still running. If your /lib directory
was damaged, then the beahviour would be similar to what you're
encountering, but then you'd have to find out why it became damaged or
corrupted in the first place (HW failure, system cracked, whatever).

If it doesn't come up again on the next reboot, it's time to use your
backups, anyway.

Michael

[Dave Brown]

You might try to boot up with a"rescue" system and see if you can mount
the filesystem. (In rescue mode, you're not using any of the installed
code, so you get a better idea of it being a hardware or
installed-software problem.)

--
Dave Brown Austin, TX

[Raqueeb Hassan]

you might like to add this drive to another linux machine and mount
that. try running fsck to check the error.

--
raqueeb hassan
congo (drc)

[Vito Corleone]

Hi Michael,

> If you're lucky, it's just a memory problem, but I fear that
> you have probably have a bad HD (the kernel error would indicate
> a problem with the filesystem used; possibly ext3).
>
> Try rebooting the machine, and check the error log. If even a simple
> /bin/ls doesn't work, then something is seriously damaged, but without
> a correctly running system, you won't get very far at this point for
> any kind of diagnosis while it is still running. If your /lib
> directory was damaged, then the beahviour would be similar to what
> you're encountering, but then you'd have to find out why it became
> damaged or corrupted in the first place (HW failure, system cracked,
> whatever).
>
> If it doesn't come up again on the next reboot, it's time to use your
> backups, anyway.

I tried to reboot, and luckily the system comes up again. How do I check
the error? Where can I find the error log?
Also, I have similar machine running kernel 2.4, the load is lower than
the machine running 2.6 (they should be the same), I don't know if this
has something to do with the error?