NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

xushi's avatar
xushi
Aspirant
Jun 04, 2016
Solved

Upgrading openssh help

Hi all,

 

I've been suffering from really slow rsync speeds when copying files from one NV+ to another. Speeds around 700k/sec compared to having a computer in between doing the copying via afp/nfs/smb (10+m/sec).

 

The issue it seems is described here - scroll down to Eirik comment. Openssh needs upgrading.

 

https://community.netgear.com/t5/Using-your-ReadyNAS/Rsync-slow-as-heck-for-everyone-else/td-p/617599/page/6#

 

I'm trying to find a good way to upgrade openssh... I installed the `apt` .bin but don't wan to `upgrade` as it will break everything..

 

I tried to `apt-get install openssh` but it couldn't find the package.


I tried to follow his steps but fails to install build-essentials.

 

# apt-get install build-essential zlib1g-dev libssl-dev
Reading Package Lists... Done
Building Dependency Tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
build-essential: Depends: libc6-dev-sparc64 but it is not going to be installed
E: Broken packages


 

Can anyone please advise or help me on getting this sorted? What can I do to get openssh upgraded?

 

These are 2 legacy ReadyNAS NV+ 4.1.14 , 1GB RAM.

 

Thanks.

  • You're just not going to get 30 MB/sec on an NV+ with rsync.  I get about 4 MB/sec on my rsync backup jobs (which uses the daemon method) - remote source is my Pro-6.  So I think the results you are getting are normal.  

     

    Eirik in the original post says he got 7.5 MB/sec, but that was his only post (ever) so we can't follow up with him.  But from the script, it appears that he built SSL, which isn't relevant if you don't use encryption.  We don't know anything about his network setup, or how much memory was in his NAS.  You could perhaps enable jumbo frames and see if you get any improvement.

     

    Apart from that I have no suggestions.

     

     

12 Replies

Replies have been turned off for this discussion
    • xushi's avatar
      xushi
      Aspirant

      I'm not fully understanding your question; Doesn't rsync connect using SSH remotely?

       

      What I'm doing is copying/moving data from one readynas (directly) to the other. For example

       

      nas1:~# rsync -av --progress --remove-source-files myFolder nas2:/media/destination/

       

      That gives me terrible speeds of about 700k/sec (NAS1 >> NAS2 or vice versa)

       

      Instead, if I use a machine in the middle (my Mac, or PC), mount both, and copy from 1 to the other the speeds are normal and significantly higher (NAS1 > Mac > NAS2 or vice versa, mounted using afp/nfs/smb). 

       

      The other post identified the issue with an old version of openssl installed on the NV+

       

      Does that answer your question?

       

      Ta.

       

    • StephenB's avatar
      StephenB
      Guru - Experienced User

      jak0lantash wrote:
      So you're using Rsync, not Rsync over SSH...

      Which means that upgrading ssl won't improve the performance - because you aren't using ssl for this anyway.

       

      What performance are you seeing?

       

       

      • xushi's avatar
        xushi
        Aspirant

        Sorry for the delay, had to sort out some cabling.


        I'm quite confused.. My understanding is that by default rsync uses SSH for its communication - regardless of the -e prefix.

        I'm reading more about it,

         

        http://linux.die.net/man/1/rsync

         

        "There are two different ways for rsync to contact a remote system: using a remote-shell program as the transport (such as ssh or rsh) or contacting an rsync daemon directly via TCP. The remote-shell transport is used whenever the source or destination path contains a single colon (:) separator after a host specification. Contacting an rsync daemon directly happens when the source or destination path contains a double colon (::) separator after a host specification, OR when an rsync://"

         

        I believe I'm using SSH, because this is how I'm running it,

         

        xn1:/media/iso# rsync -av --progress large.iso xn2:/media/Files/
        sending incremental file list
        large.iso
        21594112 3% 1.45MB/s 0:07:06


        The above just has both NASs connected via a gigabit switch via cat6. Granted I'm surprised as usually it's half that speed.

         

        NAS1 ----(1G)---- Switch ----(1G)---- NAS2

         

        While if I plug my MAC to the switch, mount both NAS's on my Mac via AFP/CIFS/NFS, drag and drop from one to the other via Finder, it's at least 10 times faster - 30MB+/sec. I could take a screenshot but it means I have to connect in the garage :)

         

        Mac ----(1G)---- Switch -----(1G)----- NAS1 and NAS2

          

         

        Edit: Here's an example from my Mac, connected via Wifi to the airport express connected via 100M link to the switch.

         

        Mac ----(wifi)--- Airport Express ------(100M) ----- Switch -------(1G)------ NAS1 and NAS2

         

         

         

        Screen Shot 2016-06-08 at 7.25.29 PM.jpg

         

        Yes it's not as fast as Gigabit ethernet, but again it's pushing some good limits with ~5.6M/sec and should show what I'm talking about when compared to the 2 NASs.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More