|
Karl Kopper wrote:
>
> > > We are doing locking with NFS (the fcntl calls from the application
> cause
> > > the Linux kernel to use statd/lockd to talk to the NAS server). I just
> > > wouldn't do locking over a WAN.
> >
> > I missed the WAN bit. So you were referring to some sort of file system
> > (distributed ?, eg AFS) spread over a WAN? I had forgotten that some
> > distributed file systems aren't local only.
> >
>
> I'm probably confused. I'm just talking about doing any type of lock
> operation over a WAN (for example an NFS client that connects to the NAS box
> over the WAN). Not really distributed content stored on direct attached disk
> on each node (though that would have to be even worse for locking over a
> WAN).
Let's see if we understand e.o.
Where you're coming from:
You don't like file locking onto a box on another network over possibly
non-dedicated links. You're happy with NFS because you have the disks local
(in some arrangement I don't know about yet) on a network that others
can't get to.
Where I'm coming from:
I think of distributed file systems as being used on machines like beowulfs
(or an LVS) where the disks are on machines on a separate and dedicated network,
that is not accessible to clients (all jobs are submitted to a master node,
and the client never sees the filesytem behind it). The people running the
beowulf have complete control over the file system(s) and network behind
the master node.
Joe
--
Joseph Mack PhD, High Performance Computing & Scientific Visualization
SAIC, Supporting the EPA Research Triangle Park, NC 919-541-0007
Federal Contact - John B. Smith 919-541-1087 - smith.johnb@xxxxxxx
|
