Without this software layer, the problem with what you are trying to accomplish is that operating systems generally do not like multiple writers to a single target without locking, since each OS wants the disk resource as its own. Also, most operating systems utilize a form of file system caching within system memory. You could turn off file system caching on the OS, but if one server happens to change the underlying inode structure of the disks, the other OS sharing that disk may crash.
You have two options for what you are trying to do:
- Use a NAS protocol like CIFS and NFS over Ethernet to access the shared "files" on the disk.
- If block access is required, implement a clustering solution on your servers.
Dig Deeper on Data storage strategy
Related Q&A from Christopher Poelker
SAN expert Chris Poelker compares connecting a SAN with wavelength cabling and dark fiber and discusses the pros and cons of each. Continue Reading
SAN expert Chris Poelker discusses how to change the size of a LUN in a Microsoft cluster server environment. Continue Reading
Storage expert Chris Poelker outlines WWN basics in order to answer the question: "Why do HBAs in a SAN have same base?" Continue Reading