Having just recommended NFS, I must respond to this question. YES, there are reasons why one might NOT want to use it.
NFS is my first choice for shared RW storage or for any shared storage where you don't have a hardware sharing option. Caleb can share the disks at the HW level, so that is preferred. So why or when would one not want to go NFS? #1 - NFS firstly requires the network. The sharing systems cannot operate independently. (They cannot be isolated. Sometimes people isolate systems. Lots of reasons for that; do I need to enumerate? And don't get me started about port-grained access controls in switches and VLANs.) The requirement for the network also affects the sequencing at startup. Your NFS-resident content cannot be there until your network is fully operational. #2 - NFS means that one server has to "own" the data. That one server becomes another single point of failure. Even apart from failure, access times are different on all the other systems so you may find performance numbers out of balance. "It depends." #3 - (related to #2) NFS and NIS historically are the two services which can lock-up a system tighter than anything else. If the hosting NFS server goes away, or if there is some other problem between there and the client(s), then the client(s) are stuck until things are restored. -- R; <>< Rick Troth Velocity Software http://www.velocitysoftware.com/ On Tue, Dec 14, 2010 at 03:47, Roger Evans <[email protected]> wrote: > Is there any reason to use anything but NFS? It's worked for years > without any problem on all sorts of linux/unix combinations. Works fine > between linux VM's on the same LPAR. Can't think of any reason it > wouldn't work between LPARS. > > Roger > > > On Mon, 2010-12-13 at 22:56 -0600, David Boyes wrote: > >> > Can anyone suggest any ways to share filesystem between lpars . thanks. >> >> NFS >> OCFS2 >> OpenAFS (lets you share far beyond lpars) >> Lustre >> OpenGFS (runs fine on z) >> >> If you need only R/O sharing, you can also implement shared r/o volumes in >> your IOCP, but updating the volume is a bit painful. >> >> ---------------------------------------------------------------------- >> For LINUX-390 subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO LINUX-390 or >> visit >> http://www.marist.edu/htbin/wlvindex?LINUX-390 >> ---------------------------------------------------------------------- >> For more information on Linux on System z, visit >> http://wiki.linuxvm.org/ > > Med vennlig hilsen > > Roger Evans > Systemkonsulent > > > ________________________________________________________________________ > AutoData Norge AS - www.autodata.no - [email protected] > > Tlf: +47 23 17 20 30 Direkte: +47 23 17 20 46 - Faks: +47 23 17 20 50 > > > > > ________________________________________________________________________ > > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
