New answers tagged upload
As EEAA said, this is definitely an inode problem. This is something you need to fix at a filesystem level. If you can't recreate the while filesystem, for example if you have all your data in one partition mounted at / [note: this is usually bad!], you can shrink the root filesystem, then create a second filesystem with appropriate inode counts from the ...
You're running out of inodes. You can verify this by running $ df -i. As far as I know, there's no way to increase the number of inodes on an already-existing filesystem. You can, however, specify a higher number of inodes at fs creation time using the -N flag for mkfs.ext4.
After a week of going crazy, I finally found the root of the problem, it turned out to be the hard disk. It was making occasional clicking noises but I thought that it would not be a problem since I was only evaluating Windows 2012. After all, Windows had loaded correctly and the only apparent problem was an occasional boot failure, but once the server ...
FYI the php.ini file says: ; Temporary directory for HTTP uploaded files (will use system default if not ; specified). ; http://php.net/upload-tmp-dir ;upload_tmp_dir = so its 'tmp' vs 'temp'. This at least worked for me.
You need to: sudo su - pip install filechunkio and then use the --multipart option of s3put.
You're probably hitting a bottleneck on the NAT instance. Driving 200 servers worth of large HTTP requests through the one server is probably taxing it too much (be it CPU or network bandwidth). Split your servers across multiple subnets with multiple NAT instances, or put them in a public subnet with direct networking to S3 rather than via a NAT.
Top 50 recent answers are included