jim at ohlste.in
Thu Aug 20 18:42:40 MSD 2009
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:
>> 220.127.116.11, server: mydomain.com, request: "GET
>> HTTP/1.1", upstream: "fastcgi://unix:/tmp/cgi.sock:", host: "mydomain.com",
>> 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 ?
2009/08/20 10:37:33 [crit] 28088#0: *1189 rename()
"/falcon/cache2/d/ad/accbc23af479834e8209b927b3beeadd" failed (18:
Invalid cross-device link) while reading upstream, client: 18.104.22.168,
server: localhost.us.com, request: "GET
HTTP/1.1", upstream: "fastcgi://unix:/tmp/cgi.sock:", host:
More information about the nginx