I'm responsible for the urging of not using "soft" in the docs. Why? It
was a never ending source of headaches -- and it took a few hours to
narrow down the problme to soft NFS mounts.
Even if you could get the WiFi to work with "soft" you WILL certainly
have problems with cluster mode with failed jobs. Dvd::rip currently
isn't smart enough to retry a failed job.
A solution that might make NFS work with hard for you is to use NFS over
TCP/IP only. Read the NFS docs for this, or the NFS Howto on tldp.org.
Mark
On Thu, 2005-08-04 at 21:09 +1000, Triffid Hunter wrote:
> Daniel Webb wrote:
> > Also, I noticed in the docs that it urges against using the NFS "soft" mount
> > option, but on my wireless LAN, NFS almost always hangs without the soft
> > option. I can't even kill -9 any process that tries to access the NFS drive
> > once that happens, and I have to reboot. Is there any way around this?
> >
>
> If you read the NFS docs, 'Hard' mode will lock processes until the NFS server
> becomes available again, marking them as waiting for I/O. 'Soft' mode, on
> the other hand, returns a file read error if the NFS server becomes
> unavailable.
>
> Hard mode is preferable as it shouldn't cause transcode processes to exit with
> errors if your wifi drops packets. If your nodes aren't detecting the
> re-appearance of your NFS server, that's a problem completely outside of
> dvd::rip. Perhaps poke around the NFS team's bugzilla and/or docs?
>
>
>
--
Mark Rose <shifted@xxxxxxxxxx>
Public key: http://shifted.ca/pubkey.asc
signature.asc
Description: This is a digitally signed message part
|