[Info-vax] NFS, indexed files and LDdriver

P. Sture paul.nospam at sture.ch
Thu Oct 22 07:42:51 EDT 2009


In article <4AE01EC8.7020904 at hrem.nano.tudelft.nl>,
 Jouk Jansen <joukj at hrem.nano.tudelft.nl> wrote:

> JF Mezei wrote:
> > I currently have a pair of IDE 30 gig drive on the alpha which serves
> > via MSCP the Vax (and the alpha, of course).
> > 
> > I am looking at options to let the VAX continue to run after the Alpha
> > has been removed.
> > 
> > I take it that indexed files cannot reside on an NFS served disk ? (for
> > instance, move all ODS directories to the unix file system, and then
> > have VAX VMS access them via NFS).
> > 
> > Can LDdriver create an LD: device that is mapped to a container file
> > served via NFS ?  If so, I could create container images of the 2 30 gig
> > drives on OS-X and then the VAX could create LD drives that were mapped
> > to those NFS-accessed container files.
> > 
> > 
> Yes I did it, but... the bottleneck is the NFS client of VMS. Presently 
>   most (all??) are still version 2 which cannot handle (cotainer)-files 
> larger than 4GB.
> 

I ran into this a couple of years ago.  Even though I set up a V3 
server, VMS would only talk to it using V2.

BACKUP /IMAGE didn't complain when I threw too large a volume at my NFS 
container, but it was easy to see that the resulting volume had "wrapped 
around".

-- 
Paul Sture



More information about the Info-vax mailing list