All, I'm using /bin/scp to transfer files between hosts.
With a file about 3.5M, scp fails with the error message
================================================== ==============
Desktop_Billable.out 60% |******** | 17272 KB 00:03
ETAbuffer_append_space: alloc 10506240 not supported
lost connection
================================================== ==============

Is this a limitation of scp or is there an issue in the system API?
When I zip the file (with either gzip or use scp -C), the transfer
succeeds.

Is this limitation in file size built in? I couldn't find any mention
in the scp man page.

Any pointers?

Thanks,
Sashi

Sashi <smalladi@gmail.com> wrote:
> All, I'm using /bin/scp to transfer files between hosts.

What OS and SSH version on both sides?

> With a file about 3.5M, scp fails with the error message
> ================================================== ==============
> Desktop_Billable.out 60% |******** | 17272 KB 00:03

17272 KB is substantially more than 3.5M...

> Is this limitation in file size built in? I couldn't find any mention
> in the scp man page.

I've transferred many gigabytes using scp. It's unlikely to be a built-in
limitation. Unfortunately, it's hard to deduce more with the very few
details you've provided.

--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/

On Jun 24, 3:47 pm, hume.spamfil...@bofh.ca wrote:
> Sashi <small...@gmail.com> wrote:
> > All, I'm using /bin/scp to transfer files between hosts.
>
> What OS and SSH version on both sides?
>
> > With a file about 3.5M, scp fails with the error message
> > ================================================== ==============
> > Desktop_Billable.out 60% |******** | 17272 KB 00:03
>
> 17272 KB is substantially more than 3.5M...
>
> > Is this limitation in file size built in? I couldn't find any mention
> > in the scp man page.
>
> I've transferred many gigabytes using scp. It's unlikely to be a built-in
> limitation. Unfortunately, it's hard to deduce more with the very few
> details you've provided.
>
> --
> Brandon Hume - hume -> BOFH.Ca,http://WWW.BOFH.Ca/

So have it and never had a problem earlier.
Here's the result of running the command in verbose mode:

debug1: Authentication succeeded (keyboard-interactive)
debug1: fd 8 setting O_NONBLOCK
debug1: fd 9 setting O_NONBLOCK
debug1: channel 0: new [client-session]
debug1: send channel open 0
debug1: Entering interactive session.
debug1: ssh_session2_setup: id 0
debug1: Sending command: scp -v -d -t /ned/data/20080615/Recovery/.
debug1: channel request 0: exec
debug1: channel 0: open confirm rwindow 100000 rmax 32768
Sending file modes: C0644 29039048 Desktop_Billable.out.csv
Desktop_Billable.out 33% |**** | 9464 KB 00:05
ETAbuffer_append_space: alloc 10498048 not supported
debug1: Calling cleanup 0x2620c(0x0)
debug1: channel_free: channel 0: client-session, nchannels 1
debug1: Calling cleanup 0x3429c(0x0)
lost connection

Sashi wrote:
> On Jun 24, 3:47 pm, hume.spamfil...@bofh.ca wrote:
>> Sashi <small...@gmail.com> wrote:
>>> All, I'm using /bin/scp to transfer files between hosts.
>> What OS and SSH version on both sides?
>>
>>> With a file about 3.5M, scp fails with the error message
>>> ================================================== ==============
>>> Desktop_Billable.out 60% |******** | 17272 KB 00:03
>> 17272 KB is substantially more than 3.5M...
>>
>>> Is this limitation in file size built in? I couldn't find any mention
>>> in the scp man page.
>> I've transferred many gigabytes using scp. It's unlikely to be a built-in
>> limitation. Unfortunately, it's hard to deduce more with the very few
>> details you've provided.
>>
>> --
>> Brandon Hume - hume -> BOFH.Ca,http://WWW.BOFH.Ca/
>
> So have it and never had a problem earlier.
> Here's the result of running the command in verbose mode:
>
> debug1: Authentication succeeded (keyboard-interactive)
> debug1: fd 8 setting O_NONBLOCK
> debug1: fd 9 setting O_NONBLOCK
> debug1: channel 0: new [client-session]
> debug1: send channel open 0
> debug1: Entering interactive session.
> debug1: ssh_session2_setup: id 0
> debug1: Sending command: scp -v -d -t /ned/data/20080615/Recovery/.
> debug1: channel request 0: exec
> debug1: channel 0: open confirm rwindow 100000 rmax 32768
> Sending file modes: C0644 29039048 Desktop_Billable.out.csv
> Desktop_Billable.out 33% |**** | 9464 KB 00:05
> ETAbuffer_append_space: alloc 10498048 not supported
> debug1: Calling cleanup 0x2620c(0x0)
> debug1: channel_free: channel 0: client-session, nchannels 1
> debug1: Calling cleanup 0x3429c(0x0)
> lost connection

Looks like the file you're sending ( Desktop_Billable.out )is still
being accessed/appended to while you're trying to transfer it.

On Jun 24, 5:47 pm, Sam N <s...@spam.unix.ms.spam> wrote:

> Looks like the file you're sending ( Desktop_Billable.out )is still
> being accessed/appended to while you're trying to transfer it.

I don't think. Sending it with the -C option or zipping it up first
works.

Sashi wrote:
> On Jun 24, 5:47 pm, Sam N <s...@spam.unix.ms.spam> wrote:
>
>> Looks like the file you're sending ( Desktop_Billable.out )is still
>> being accessed/appended to while you're trying to transfer it.
>
> I don't think. Sending it with the -C option or zipping it up first
> works.

...........