Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[yescabernetnointernet]

Hey Roman, any advices about NFS (Network File System) shares when using clrmamepro?

Any programs of any kinds I use they all work seamless on files remotely stored on my server via NFS share: I can play music / film via VLC with no issues at all, I can convert video / audio files, read+write Steam Library, etc...

See: https://www.emulab.it/forum/index.php?topic=6308.msg21189#msg21189
With clrmamepro I have problems with write operations (read operations are good and work just fine).
As soon clrmamepro needs to perform a write (Fix, Copy, etc...) it tries but suddenly get stuck forever and then goes into "Non Responding".
There is no way at all to close it, neither shutting down Windows will work because it will stay on trying to close clrmamepro. Nor I can unmount the share, Windows simply get stuck at trying it.

The only way to close / kill clrmamepro (or Windows) is to shutdown the server.

Code: [Select]

Locale    Remoto                                 Proprietà
-------------------------------------------------------------------------------
S:       \\SERVERNFS\path\to\share           UID=1000, GID=1000
                                                rsize=1048576, wsize=1048576
                                                mount=soft, timeout=1.6
                                                retry=1, locking=yes
                                                fileaccess=755, lang=ANSI
                                                casesensitive=no
                                                sec=sys

Any suggestions?

[Roman]

Check access writes maybe Sounds too easy but actually I don't have an idea what else should have caused this. Would be interesting if you play a bit with a minimal setup, e.g. a 1-set-1-rom datfile which you create on your own, put the file on your share and do some testing with renames/write access.

[yescabernetnointernet]

Check access writes maybe Sounds too easy but actually I don't have an idea what else should have caused this. Would be interesting if you play a bit with a minimal setup, e.g. a 1-set-1-rom datfile which you create on your own, put the file on your share and do some testing with renames/write access.

It was not a write issue at all...

Don't ask my why / how, but... This works fine:

Code: [Select]

mount -o anon mtype=hard timeout=20 nolock SERVER_IP:/path/to/NFS/shared/folder {driveletter}:
 
SOLVED!
For future readers: when mounting a NFS share use mtype=hard and nolock options (see here)!
IMPORTANT: be sure to have a stable and reliable connection between SERVER and CLIENT when using mtype=hard!!

hard or soft — Specifies whether the program using a file via an NFS connection should stop and wait (hard) for the server to come back online, if the host serving the exported file system is unavailable, or if it should report an error (soft).

If hard is specified, the user cannot terminate the process waiting for the NFS communication to resume unless the intr option is also specified.

If soft is specified, the user can set an additional timeo=<value> option, where <value> specifies the number of seconds to pass before the error is reported.

SOURCE

[Roman]

very interesting, thanks