[Leaplist] Any suggestions on resolving "Stale NFS file handle" errors?

[Andrew]

On Dec 13, 2008, at 1:43 AM, Damien McKenna wrote:

> On Dec 9, 2008, at 8:26 PM, Bryan J Smith wrote:
>> In other words, when I re-read your message, and saw that you were
>> mounting web content "rw" and not "ro," then red flags went way  
>> up.  If
>> you're round-robin serving, then your servers are stomping on each
>> others write locks, and rather quickly.  ;)
>
> The files which are causing the major problem are all in one  
> subdirectory (/opt/httpd/htdocs/mysite/coolstuff/), but the entire  
> directory is being mapped several levels up (/opt/httpd/htdocs) so  
> I don't know if it's going to be feasible to redo it given there  
> are several sites running on the same cluster, or if they're going  
> to want to.

While moving to a setup where there is only 1 writer and multiple  
readers is your best strategy, in the near term you might want to try  
setting some of the timeout/caching options lower than their defaults.

You can start with actimeo to see if it helps, and then if it does,  
you can try the acdir/acreg min/max values individually to see which  
one helps the most.  Another option to look at is noac -- it's  
intended for this type of situation, but you take a performance hit  
when you use it;  of course, working slower is better than broken.



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.