Repeated 400 Bad Request errors about s3backer HOT 11 CLOSED

I have reproduced this error and it seems to be fixed by the attached patch. 
Please
test this out and confirm it fixes the problem for you too. Thanks for the bug 
report.

Not quite fixed.

Yes, looped 400 errors no longer happen.

But sometimes that block where failure happened is not updated.
And some kind of raw S3 response goes to the log (with error that is ignored).

Bucket is empty and I am writing with dd.

Look at the log:

2008-07-11 15:14:59 INFO: retrying query (attempt #19): PUT
http://s3.amazonaws.com/du-backup4/macos0000003a
<Error><Code>AccessDenied</Code><Message>Access
Denied</Message><RequestId>A0A999C258EC4C0A</RequestId><HostId>qvZCP8r8gna5Cq9Xq
fuJbm9ysFyDmNbRkRKxg7I6DtjTBdGKDka0QuW65iCNGHV9</HostId></Error><?xml
version="1.0" encoding="UTF-8"?>
2008-07-11 15:14:59 DEBUG: success: PUT 
http://s3.amazonaws.com/du-backup4/macos0000003a
   WRITE[0] 4096 bytes
   unique: 15, error: 0 (Unknown error: 0), outsize: 24
unique: 15, opcode: WRITE (16), nodeid: 2, insize: 4160

And after that there is no block macos0000003a in a bucket at all.

The same thing happens with full bucket. File system thinks block has been 
updated
but it is not.

My apologies, previous fix was incomplete. I have committed a better fix in r92.
Please try it out.

Note: changes include a change to configure.ac, which requires regenerating the
autofoo stuff (use autogen.sh). Alternately, you can try this simply by 
downloading
the latest version of s3backer.c from
http://s3backer.googlecode.com/svn/trunk/s3backer.c and then manually adding
"-fnested-functions" to CFLAGS (if using MacOS).

Yes. No It works better.
But now I can't start it without "-d -f" flags - on first request s3backer 
crashes.
Crash report included.

This time the problem is that Mac OS barfs on GCC nested functions. I've 
refactored
s3backer.c to not use them in r98. Please give it a try. Thanks.

Looks good! Thanks!