Print

Print
hi darren,

thanks for your reply...

i have gotten more answers now, and in order to put this information in a place where it can be most easily found by others, i will post all that i know in here.

the issue only appears on solaris (not linux or macosx) so that's why it didn't happen to your install.

here is the pertinent info from my email back from the mathworks:

...when using the standard file browsing dialog, (i.e. the dialog displayed when selecting "Open" from MATLAB's File menu) some directories showed up empty?  Is this correct?

From my understanding, the source of the trouble may have been the file server's checkpoint files.  In NFS 3, these files use 64-bit inodes, and MATLAB appears to be unable to handle 64-bit inode sizes.  Presumably, that is why forcing your system to use NFS 2 resolved the issue.  However, you should be able to resolve the issue in NFS 3 if you do one of the following configure the file server to hide the checkpoint files.  You should be able to achieve this by adding the "32bitclients" option to the /etc/exports file on the machine where the files are stored.

as solaris support is being phased out for future matlab releases, there are no plans to fix the issue.

thanks for your help

-lokke

On Mar 12, 2009, at 1:07 PM, Darren Gitelman wrote:

Hi Lokke

I am running NSFv3 on redhat linux enterprise 5 and it works fine with
SPM. I tried NSFv4 for a time, but switched back to 3 for reasons
unrelated to SPM. Anyway it also worked. I can't comment on whether
there are performance differences, but I didn't notice anyting
obvious.

darren

On Thu, Mar 12, 2009 at 12:00 PM, Lokke Highstein <[log in to unmask]> wrote:
hello SPM list,
almost two years ago, i was setting up new storage for my lab, and
encountered a strange error, where NFS mounted directories would be
available from the command line, but within the SPM gui, they would not show
up at all.
i called up the mathworks and they managed to find a bug report somewhere
that said that this was a known bug, and that if i switched to NFSv2 the
problem would go away.  so i did change the NFS version to v2, and the
problem went away.
however, now i am shopping for new storage, and find that on the product i
want, NFS v2 is no longer an option, it only offers NFS v3 or v4.
what i am trying to figure out is if this bug has been worked out, or if it
is going to be a huge problem for me.
at this point, short of setting up a test server running NFS v4 and mounting
a share, i don't know how to test this, so before i start in on that, i
thought i would ask this list if it is a known issue, and if so, if it has
been fixed in any of the SPM5 updates (or in SPM8)
thanks for your help,

Lokke Highstein
Systems Manager, Program For Imaging and Cognitive Sciences (PICS)
Columbia University
212-342-0293
[log in to unmask]




-- 
-----
Darren Gitelman


Lokke Highstein
Systems Manager, Program For Imaging and Cognitive Sciences (PICS)
Columbia University
212-342-0293