At around 7:00pm GMT November 21, our website became inaccessible for 1 hour. Again, we are deeply sorry for the downtime. What happened was that our Network File system became unmountable and needed a reboot.The majority of data are stored in the database. The rest are caches of temporary data in the form of files.When you have one web server, you can put all those files into that server’s local file system. When you have more than one, you need to put the files where all the web servers can access.One of the easier ways is to use a Network File system (NFS). With NFS, the web servers will the folders on the shared file server as if they are local.The biggest drawback of NFS is that, when something goes wrong, and the shared file server became unmountable, the web servers will stop, as if there’s something wrong with their “real” local file systems. In short, it drags everyone down.To make things worse, with this type of error, we cannot display anything friendlier than the discomfortingly-worded “Service unavailable : Internal error : 132″ page.We have been moving away from NFS recently but there are still some older stuffs that we haven’t converted. Rest assured we’ll be speeding up to achieve independence from NFS these couple days.