All files from this thread

File Name	File Size		Posted by	Date
patch.short.write	3.9 KB	open | download	Igor Sysoev	09/25/2009	Read message
patch.short.write1	4.7 KB	open | download	Igor Sysoev	09/25/2009	Read message

> What does "ulimit -f" show on these servers ?

Unlimited in both.

Igor Sysoev wrote:
> On Fri, Sep 25, 2009 at 10:10:45AM +0400, Igor Sysoev wrote:
>
>> > > bytes actually written. This number is less than or equal to nbyte.
>>
>> Could you try the attached patch. It retries short write.
>
> Sorry, this patch is wrong. Try the new attached one.

We are getting there...

2009/09/25 12:54:37 [crit] 18192#0: *35 pwrite()
"/usr/local/nginx/client_body_temp/0000000002" has written only 274432
of 524288, client: 10.100.0.115, server: contentdata.spacash.com,
request: "POST /store.php HTTP/1.1", host: "10.100.0.155"
2009/09/25 12:54:37 [crit] 18192#0: *35 pwrite()
"/usr/local/nginx/client_body_temp/0000000002" failed (28: No space left
on device), client: 10.100.0.115, server: contentdata.spacash.com,
request: "POST /store.php HTTP/1.1", host: "10.100.0.155"

No space left on device. I thought setting the upload path at php.ini
would be enough, but it seems nginx first stores the files in that
"client_body_temp" directory and then moved to php's temporary uploaded
file location.

Is that configurable for nginx? It would be nice if the "copy" could be
avoided, as i have the temporary uploaded file location por php in a
different partition (where i have plenty of space left).

Thank you for the patch, and your time.

Alejandro Martínez Lanfranco
--
Posted via http://www.ruby-forum.com/.