samba - Dec 2016 - Very very slow SAMBA sharing on Ubuntu (with StorjShare-CLI)

I’m using a decentralized data storage application named StorjShare-CLI :
https://github.com/Storj/storjshare-cli

This application store data into « nodes ». StorjShare-CLI can run 1 or
several « nodes » in order to store data located at different places.


On a given Ubuntu machine I’m running both nodes located on this machine
AND also nodes located on another machine (a Netgear ReadyNAS) thanks to a
SAMBA sharing …

If the nodes located on the local machine are growing normally (few GB a
day), nodes located on the SAMBA sharing are growing very very slowly (few
MB a day)


Here is the line I have in my /etc/fstab

===============================================================================
…

//192.168.0.10/DataFarming/ /DataFarming/ReadyNAS cifs
guest,iocharset=utf8,gui=100,uid=1000,_netdev 0 0

===============================================================================
Is there any optimization to make in this line ?

Is there any « tweak » to do on the ReadyNAS side ?

On 12/04/2016 03:37 AM, Bernard Chabot via samba wrote:
> I’m using a decentralized data storage application named StorjShare-CLI :
> https://github.com/Storj/storjshare-cli
>
> This application store data into « nodes ». StorjShare-CLI can run 1 or
> several « nodes » in order to store data located at different places.
>
>
> On a given Ubuntu machine I’m running both nodes located on this machine
> AND also nodes located on another machine (a Netgear ReadyNAS) thanks to a
> SAMBA sharing …
>
> If the nodes located on the local machine are growing normally (few GB a
> day), nodes located on the SAMBA sharing are growing very very slowly (few
> MB a day)
>
>
> Here is the line I have in my /etc/fstab
>
>
===============================================================================>
> …
>
> //192.168.0.10/DataFarming/ /DataFarming/ReadyNAS cifs
> guest,iocharset=utf8,gui=100,uid=1000,_netdev 0 0
>
>
===============================================================================>
> Is there any optimization to make in this line ?
>
> Is there any « tweak » to do on the ReadyNAS side ?
Try this.

On your server side, add 127.0.0.1 to /etc/hosts.  Mine look like this.  Get
the first entry below (server.acme.local) with the "hostname" command.

127.0.0.1   server.acme.local localhost localhost.localdomain localhost4 
loca
lhost4.localdomain4

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

On Mon, 5 Dec 2016 00:41:35 -0800
ToddAndMargo via samba <samba at lists.samba.org> wrote:
> On 12/04/2016 03:37 AM, Bernard Chabot via samba wrote:
> > I’m using a decentralized data storage application named
> > StorjShare-CLI : https://github.com/Storj/storjshare-cli
> >
> > This application store data into « nodes ». StorjShare-CLI can run
> > 1 or several « nodes » in order to store data located at different
> > places.
> >
> >
> > On a given Ubuntu machine I’m running both nodes located on this
> > machine AND also nodes located on another machine (a Netgear
> > ReadyNAS) thanks to a SAMBA sharing …
> >
> > If the nodes located on the local machine are growing normally (few
> > GB a day), nodes located on the SAMBA sharing are growing very very
> > slowly (few MB a day)
> >
> >
> > Here is the line I have in my /etc/fstab
> >
> >
===============================================================================>
>
> > …
> >
> > //192.168.0.10/DataFarming/ /DataFarming/ReadyNAS cifs
> > guest,iocharset=utf8,gui=100,uid=1000,_netdev 0 0
> >
> >
===============================================================================>
>
> > Is there any optimization to make in this line ?
> >
> > Is there any « tweak » to do on the ReadyNAS side ?
> Try this.
> 
> On your server side, add 127.0.0.1 to /etc/hosts.  Mine look like
> this.  Get the first entry below (server.acme.local) with the
> "hostname" command.
> 
> 127.0.0.1   server.acme.local localhost localhost.localdomain
> localhost4 loca
> lhost4.localdomain4
> 
Please don't do this, '127.0.0.1' should only point to
'localhost'.

If your server gets its IP via DHCP (it shouldn't) you only need:

127.0.0.1	localhost

If it has a fixed IP (as it should) you need:

127.0.0.1	localhost
192.168.0.10	server.acme.tld	server

Where '192.168.0.10' is the ipaddress of the server and
'server.acme.tld' is the FQDN of the server

Rowland