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 this is logged elsewhere ?
Tom > > Running any command that requires write access on the disk (touch > > /tmp/foo for instance) results in " Input/output error". The only way > > I've found so far to get back to normal operation is to hard reboot > > the machine. After the reboot, the system works fine for a > > day/week/month and the same problem occurs again. > Tom, > As a first step towards solving this you need to run a manual > fsck against your filesystem to see if there is anything > wrong with it. Some filesystem corruption may be triggering > the problem you're seeing. I'm pretty sure other people have > seen the exact same problem as you. > Cheers, > Sean > -- > redhat-list mailing list > unsubscribe mailto:[EMAIL PROTECTED] > https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
