Comment 2 for bug 1594739
Revision history for this message
| Alistair Coles (alistair-coles) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
Confirmed using the method Kota describes to reproduce.
The problem can also be observed by running this functional test with an EC policy:
nosetests test/functional
which does PUTs with content-length >0 but then sends no data and the client disconnects - the object servers will report 408 after 60 second timeout.
If fallocate is enabled then I believe that the bytes fallocate'd for the tmp file that the object server never writes into will be reserved until the connection is closed i.e. 60 secs by default, which is unfortunate if the declared content-length is large.
Consequently that func test may fail on an SAIO where the available filesystem space is less than that required to fallocate space for 4 max file size objects.