[MINC-development] me, I'm stumped

Steve ROBBINS minc-development@bic.mni.mcgill.ca
Thu, 1 May 2003 11:59:20 -0400


On Thu, May 01, 2003 at 11:55:20AM -0400, Jean-Francois Malouin wrote:
> * Jason Lerch (jason@bic.mni.mcgill.ca) [20030501 11:44] thus spake:
> > Ok, this is even more messed up than I first expected:
> > 
> > this works:
> > 
> > rawtominc -byte -clobber -input /dev/null /tmp/junk.mnc 470 2400 2800
> > 
> > this does not:
> > 
> > rawtominc -byte -clobber -input /dev/null /data/rome/temp/jason/test.mnc
> > 470 2400 2800
> > 
> > So ... on a local filesystem everything appears to be OK (I have not yet
> > waited long enough to check whether the file actually holds sensible
> > values when I do this with real data - it is running now, but will take
> > a while), but over NFS it fails at 2GB. I'm running the commands on
> > yorick.
> > 
> > So I've cc-ed this to the trinity (are any of you on this list) - any
> > ideas why?
> 
> yes. I knew it right away but I've been busy with bullcalf and bottom.
> XFS NFS filesystems are exported 32bits to all clients.
> We could try 64bits exports but there have been numerous problems
> before...
 
The nfs faq claims that the problems can be solved if you
use naming version 2.  Have you tried that?

    http://nfs.sourceforge.net/nfs-howto/interop.html#IRIX

-S