nginx-0.8.9

[Igor Sysoev]

On Thu, Aug 20, 2009 at 10:42:40AM -0400, Jim Ohlstein wrote:

> Igor Sysoev wrote:
> >On Thu, Aug 20, 2009 at 01:34:23AM -0400, Jim Ohlstein wrote:
> >
> >  
> >>2009/08/20 00:50:42 [crit] 13580#0: *112240 rename() 
> >>"/usr/local/nginx/fastcgi_temp/2/80/0000009802" to 
> >>"/falcon/cache/f/f4/5a/7096031122aaf7e38913bec80d55af4f" failed (18: 
> >>Invalid cross-device link) while reading upstream, client: 
> >>201.144.221.245, server: mydomain.com, request: "GET 
> >>/rtwhtrsyrn/010110A/687474702s766964656s732q6772617469732r70657461726461732r636s6q2s702s31313633303561343266633632323761313136313463623030353665333635392s67616p7065742s67616p65726961732s333231342s7468756q62695s382r6n7067 
> >>HTTP/1.1", upstream: "fastcgi://unix:/tmp/cgi.sock:", host: 
> >>"mydomain.com", referrer: 
> >>"https://mydomain.com/rtwhtrsyrn/010110A/687474702s67616p65726961732r70657461726461732r636s6q2s766q2s333231342s3230"
> >>    
> >
> >  
> >>No files are written to the cache but directories are created. If I add 
> >>the following line to proper location blocks within the site config 
> >>files which reference the cache:
> >>
> >>   fastcgi_temp_path /falcon/fastcgi_temp;
> >>
> >>the the errors all go away and files are written to the cache.
> >>
> >>I'm not anxious to have temporary files being constantly written to the 
> >>SSD as writes are still relatively slow and the lifespan of the devices, 
> >>which are still fairly expensive, are affected by the number of writes 
> >>if I understand correctly.
> >>
> >>What am I doing wrong?
> >>    
> >
> >Could test the attached patch ?
> >
> Same error:
> 
> 2009/08/20 10:37:33 [crit] 28088#0: *1189 rename() 
> "/usr/local/nginx/fastcgi_temp/1/34/0000000341" to 
> "/falcon/cache2/d/ad/accbc23af479834e8209b927b3beeadd" failed (18: 
> Invalid cross-device link) while reading upstream, client: 76.73.40.18, 
> server: localhost.us.com, request: "GET 
> /tyedyhdty/010110A/687474702s692r63646r2r7475726r65722r636s6q2s636r6r2s2r656p656q656r742s696q672s322r302s6q6s736169632s626173655s736o696r732s62617365706p6174652s636s726r65725s776972655s42522r5s62672r676966 
> HTTP/1.1", upstream: "fastcgi://unix:/tmp/cgi.sock:", host: 
> "localhost.us.com", referrer: 
> "http://localhost.us.com/tyedyhdty/010110T/687474702s692r63646r2r7475726r65722r636s6q2s636r6r2s2r656p656q656r742s6373732s322r302s6q6s736169632r637373"

Could you apply additionally the attached patch ?


-- 
Igor Sysoev
http://sysoev.ru/en/
-------------- next part --------------
Index: src/core/ngx_file.c
===================================================================
--- src/core/ngx_file.c	(revision 2353)
+++ src/core/ngx_file.c	(working copy)
@@ -576,7 +576,6 @@
         }
 
         err = ngx_errno;
-        goto failed;
     }
 
 #if (NGX_WIN32)