On 3/28/2017 5:24 AM, Harry Putnam wrote:
> Timothy Coalson writes:
>
>> On Mon, Mar 27, 2017 at 9:44 PM, Harry Putnam wrote:
>>
>>> Geoff Nordli writes:
>>>
>>> [...]
>>>
Just a thought here, you may want to try a different ssh
>
Re busy
What about loop back mounts?
Any shares of any type?
Anything like that?
Re failed service
The local fs error maybe because the system is trying to mount a fs on top of a
non-empty directory or equivalently two file systems have the same mount point.
On 2017-03-27 09:33 PM, Timothy Coalson wrote:
On Mon, Mar 27, 2017 at 9:44 PM, Harry Putnam wrote:
Geoff Nordli writes:
[...]
Just a thought here, you may want to try a different ssh cipher. Give
arcfour a try and see if that is fast enough for you.
Harry Putnam writes:
> I tried this at ~/.ssh/config on source host. The host named
> in the config is the destination host that is running the rsync cmd.
>
> Host g1 <= name of linux host
> HostName g1.local.lan <=same linux host
> Ciphers arcfour
Nevermind
Geoff Nordli writes:
> On 2017-03-27 07:44 PM, Harry Putnam wrote:
>> Geoff Nordli writes:
>>
>> [...]
>>
>>> Just a thought here, you may want to try a different ssh cipher. Give
>>> arcfour a try and see if that is fast enough for you.
>>>
>> Can that be done
Harry Putnam writes:
> I think what Timothy C has in mind is dropping mbuffer/tamp and using
> ssh for the whole thing
>
> zfs send p/fs@now | ssh RECV_HOST zfs recv p/fs
OOps that should have read ...
I think what Geoff N has in mind [...]
Timothy Coalson writes:
> On Mon, Mar 27, 2017 at 9:44 PM, Harry Putnam wrote:
>
>> Geoff Nordli writes:
>>
>> [...]
>>
>> >
>> > Just a thought here, you may want to try a different ssh cipher. Give
>> > arcfour a try and see if that is