<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Steffen Grunewald wrote: <blockquote cite="mid20050331123146.GU12331@debian-server.aei.mpg.de" type="cite"> <pre wrap="">On Thu, Mar 31, 2005 at 01:57:03PM +0200, Jeroen Wunnink wrote: </pre> <blockquote type="cite"> <pre wrap="">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.. </pre> </blockquote> <pre wrap=""> Additional advice: get the smartmontools package and run disk selftests periodically. (smartmontools.sourceforge.net) </pre> </blockquote> Also, depending on your disk requirements, consider moving to RAID. On the low-end side, a 3ware 2port ATA RAID card for ~$100 and two 40gig drives for $50 each works well. David Hiltz </body> </html>