On Thu, Mar 31, 2005 at 01:57:03PM +0200, Jeroen Wunnink wrote: > This usually means the filesystem jumps into read only mode because some fs > errors have occured. > We've had this problem last month with a server, and it ended up that the > harddisk was going bad. > > You can try to remount the filesystem first: 'mount -o remount /home' for > example and see if that solves it.. > > If not, you can try to unmount the filesystem directly if possible (make > sure there's no processes keeping it occupied) and do a e2fsck on it, or > reboot it in single user mode and then fsck all filesystems if it concerns > / or /boot for example.. > > It may solve it, but big chance that it'll pop back in read only mode after > a while again.. > > Advice: back up the system and go swap the harddisk.. Additional advice: get the smartmontools package and run disk selftests periodically. (smartmontools.sourceforge.net) Cheers, Steffen -- Steffen Grunewald * MPI fuer Gravitationsphysik (Albert-Einstein-Institut) SciencePark Golm, Am Mühlenberg 1, D-14476 Potsdam * http://www.aei.mpg.de * e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298} No Word/PPT mails - http://www.gnu.org/philosophy/no-word-attachments.html -- fedora-legacy-list@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-legacy-list
