Zatara file-system errors
Posted (March 10th, 2010 at 12:53 am PST) by SandonThe web-server “Zatara” was getting some file-system errors and thus remounted itself in to RO (read-only) mode. Because of the errors an fsck (file-system check) needs to be ran on it which can take anywhere from 1-5 hours (depending on the amount of data on the machine) in which time customer data and web-sites hosted off the machine will be down. More updates to come as progress is made on the FSCK.
Update: 03:42 AM PST: The first pass has finished which typically manes this is around 50% complete.
Update: 08:05 AM PST: The FSCK has finished and these issues should be resolved now. We’ve tested several sites and verified that everything is back up and running. If your site is on this server and you’re getting a bad_httpd_conf error still, be sure to clear out your browsers cache. If you have any further issues, please contact support.
9 Responses to “Zatara file-system errors”
Use reiserfs ! 
The site not working anyway not from ANY browsers on my computer not from other computers 
My clients are screaming my ears off. Uptime guarantee?? I’m going to have to move to Verio hosting at this rate… I have emptied cache multiple times and none of my clients’ sites work in any of our browsers.
Yeah, my site is still not up either. Clearing the cache in my “browser” does nothing except make me waste more time. This is pretty ridiculous that this has been doing on for 12 hours now.
Thanks It On now
none of my sites working on the pristine web server.
Pristina, not pristine.
manes? or means?
“arataz eb delaeh!”
There you go, that should do it.