This content has been marked as final. Show 5 replies
Never use "soft" NFS mounts unless you're absolutely sure single every application on your system is properly coded to handle failed returns from read() and write() calls every single time those calls are made, and you're willing to deal with apps running from binaries/shared objects on NFS-mounted file systems failing and dropping core files all over the place when they SIGSEGV or SIGBUS when their underlying mmap()'d binary/shared object can't be accessed and the access returns a failure.
If any of your applications are not properly coded to handle failed read() or write() calls every single time they make those calls, you may very will wind up with data corruption as those apps ignore failed IO calls.
And network hiccups causing apps to crash is probably not an issue you want to deal with.
dushank wrote:Background mounts will allow the mount to fail and it will keep retrying it in the "Background" until it succeeds or timesout. Head the warning from Andrew on soft mounts. I've always used them in conjunction.
Thank you for the reply.
But sorry but I didn't get your solution completely. Could you please explain how to do it ?
Thanks in advance,
Or try the man pages.