On Sun, 2008-12-07 at 14:26 -0500, Dustin J. Mitchell wrote:
> On Sun, Dec 7, 2008 at 1:37 PM, Matt Burkhardt <[EMAIL PROTECTED]> wrote:
> > localhost /samba/bigdrive/Music lev 0: partial taper: While writing data
> > block to S3: Too many retries; last message was 'Your socket connection to
> > the server was not read from or written to within the timeout period. Idle
> > connections will be closed.' (RequestTimeout) (HTTP 400) (after 14 retries)
>
> Hmm, I recall having this kind of trouble way back when S3 was still
> in beta, but haven't seen it since. I assumed it was due to a bug on
> the Amazon side.
>
> The S3 device does not begin sending data until it has a full block
> available, and then sends that block as quickly as the network will
> permit, so this sort of timeout cannot be caused by slowness on the
> client or anything like that.
>
> Have you modified your blocksize from the default 10M?
No, I've left it based on the examples from Amanda - here's what's in my
amanda.conf
define tapetype HARDDISK {
comment "Virtual Tapes"
length 100000 mbytes
}
> Is there some
> reason that a TCP connection to Amazon would stall out for more than
> 60 seconds?
I've got Verizon DSL - seems to be working fine - so not likely
> Can you upload multi-megabyte files to S3 using other
> utilities (e.g., JetS3t)?
I've been able to back up my document portion of my server on a regular
basis - it's uploading and storing about a little over 1GB on S3 and it
seems to work fine. For the music backup, it's gotten up to file 1c4 -
about 4.7 GB
>
> Dustin
>
Matt Burkhardt, MSTM
President
Impari Systems, Inc.
502 Fairview Avenue
Frederick, MD 21701
[EMAIL PROTECTED]
www.imparisystems.com
(301) 682-7901
