>
> > Running any command that requires write access on the disk (touch
> > /tmp/foo for instance) results in " Input/output error".
> What's "dmesg" say at that point? If you can't run dmesg, look at the
> "messages" log after you reboot to see if the kernel logged any errors
> prior to the
As I do not have any physical access to the server, I touched /forcefsck
and reboot the server. Surprinsingly, I didn't find any fsck related logs in the
different log files (boot.log, dmesg, messages.log). The fsck must have been
performed since the /forcefsck has been removed.
Do you know if th
Leseney Thomas wrote:
Running any command that requires write access on the disk (touch
/tmp/foo for instance) results in " Input/output error".
What's "dmesg" say at that point? If you can't run dmesg, look at the
"messages" log after you reboot to see if the kernel logged any errors
prior to t
On Mon, 18 Aug 2003 16:55:26 +0200
Leseney Thomas <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I rent a dedicated server (running RH 8.0) and every now and then, I
> get this error on bash command line.
>
> Running any command that requires write access on the disk (touch
> /tmp/foo for instance) res
