Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm looking for a better way of doing things than using a SAN lun mounted to multiple webservers as a way of keeping data in sync. The applications require instantaneous or near instantaneous synchronization between webservers to function, and can't be modified to work another way. OC2FS on an iscsi SAN is a good way to do it, but it still leaves the lun as a single point of failure. For example, if for some reason filesystem level corruption happens, you need to mount it as read only on all webservers so you can fsck it, which is not acceptable in my application. If you sync it over to a spare lun as a cold spare with say, drdb, which you could switch to manually and fsck the original, you sync the corruption over as well, and run into problems with your data on the original getting out of sync with your backup lun.

Is there a better way to provide some reduction in downtime in the case of problems with the SAN?

share|improve this question
What OS are the web servers running? – mrdenny Apr 18 '12 at 22:32
debian 6.0 squeeze – user1238763 Apr 19 '12 at 21:36

if SAN goes down and all of your web server resides on SAN then you pretty much out of other options unless you get yourself a redundant SAN that would work for you in case if first SAN is down.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.