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 ?
--
Igor Sysoev
http://sysoev.ru/en/