[Samba] Very very slow SAMBA sharing on Ubuntu (with StorjShare-CLI)

Rowland Penny rpenny at samba.org
Mon Dec 5 12:07:43 UTC 2016


On Mon, 5 Dec 2016 02:53:50 -0800
ToddAndMargo via samba <samba at lists.samba.org> wrote:

> On 12/05/2016 01:06 AM, Rowland Penny via samba wrote:
> > 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:
> 
> Yes and it is suppose to.  In my instance, I am using
> a fixed IP.  Without the entry you don't like, the server is
> excruciatingly slow.  So until the misunderstand or bug
> gets fixed ...

127.0.0.1 is the loopback address and should only point to localhost,
your computer will also have its own ipaddress and this should point to
the computers FQDN. If this doesn't work for you, then there is
something wrong with your setup, it is not a Samba problem.

Rowland




More information about the samba mailing list