similar to: Horrendously slow transfer speeds in FC3 is drivingmecrazy!!! Please help... - SOLVED!

Does SMB need Push bits acknowledged? I had a similar problem with sloooow printing on OpenBSD, and had to set the AckOnPush parameter to enabled. That cured the printing issue for me. Just a thought... Jim > -----Original Message----- > From: Al [mailto:alsalooq@socal.rr.com] > Sent: Monday, June 06, 2005 4:44 PM > To: samba@lists.samba.org > Subject: [Samba] Re: Horrendously

I found that for a modern PC running zero loads, (my server is a P4 3.2 with 512 M dual channel RAM an Intel Etherpro Express 100 nic, serving cached disk files from RAM) samba could be 30% slower than it should be. It would serve data at about 7 MBytes/sec compared with the old NT4 sever (same Intel nic, 512 RAM, P2/266 Cpu, NT4 with SP6a) that would do it at 10 Mbytes/sec under all

Ok, I've found some references to this issue with samba on the net, but not related to the version of samba I'm running (which is 3.0.10, updated version that comes with Fedora Core 3). My problem is this, I've got a Compaq Proliant 2500 (dual Pentium Pro-200MHz with 256MB RAM and the standard Netintelligent 10/100 network controller that come with it)... I've narrowed down that

I''m using Camping (though I suspect this applies to RoR just as well, and if you have an RoR specific answer I''d be happy to hear it, I may switch) to do a number of things for an internal application, one of which is transferring large files (~2GB each) between machines over the network. I thought the easy route would just be to make an app that when given the filename, serves

Hi, I am running an old CentOS 4 server with samba 3.4.9 and am trying to move to a new server running Centos 6 and the latest stock samba 3.5.10-125. Upon trying to switch over to the new server, I noticed that accessing shares and copying files worked perfectly fine, however upon login off, the roaming profile fails with error message: Your roaming profile was not completely synchronized.

On 03-Jun-2017 3:27 AM, "Diego Remolina" <dijuremo at gmail.com> wrote: Hi everyone, Is there anything else we could do to check on this problem and try to fix it? The issue is definitively related to either the samba vfs gluster plugin or gluster itself. I am not sure how to pin it down futher. I don't think it is vfs plugin because you haven't updated samba packages

Peter, I have the similar issues with OpenBSD and Samba. I've detailed the revs in previous posts to the newsgroup. In my case one device, a Audiotron, can stream wav files fine from a windows share on a windows box, but not from a Samba share. Windows boxes can stream fine from the same Samba share. My attempts at oplock, etc. have had no effect. If you figure this out please let me

Trying to revive this old thread as problems continue. I have noticed from the gluster logs the following on m y volume called export: [2017-08-16 20:08:47.663908] I [MSGID: 109066] [dht-rename.c:1608:dht_rename] 0-export-dht: renaming /projects/ACTIVE/Automotive/JEEP/Brand Image Program June 2016/04_Western Region/Huntington Beach CDJR - Huntington Beach, CA/04 REVIT AND CAD/2017-08-16 CAD dwgs

Hi everyone, Is there anything else we could do to check on this problem and try to fix it? The issue is definitively related to either the samba vfs gluster plugin or gluster itself. I am not sure how to pin it down futher. I went ahead and created a new share in the samba server which is on a local filesystem where the OS is installed, not part of gluster: # mount | grep home ]# ls -ld /home

Thanks for taking the time to look into this. Since we needed downtime due to the gluster update, we also updated the OS, including samba. We went from 4.2.x to 4.4.4 and many other packages for CentOS were updated as well. OS and samba updates were installed, then server rebooted, then gluster was updated. Created a new test samba share to minimize logs, etc: [VfsGluster] path = /vfsgluster

Hello all, I'm creating a site where people can share their benchmarks. If you are interested, the site is at (I just started on it so it has the stock graphics and color scheme still): www.dcsnow.com/mambo I would like some thoughts on what would be a good way to standardize the testing so the results are more comparable. Is Bonnie+ a good program for hard drive speed testing? Is there

Did the logs provide any hints as to what the issue may be? Diego On Sat, Jun 3, 2017 at 12:16 PM, Diego Remolina <dijuremo at gmail.com> wrote: > Thanks for taking the time to look into this. Since we needed downtime > due to the gluster update, we also updated the OS, including samba. We > went from 4.2.x to 4.4.4 and many other packages for CentOS were > updated as well. OS

A month ago I mentioned on this list work on a automated package deployment tool for Windows systems, which is server agnostic. At the time, I didn't have the time to put it up in a place for public consumption. I do now. The utility is named wpkg (punny isn't it?) It's nothing more than a simple .js (jscript) file which needs to be run on Windows, from a directory containing three

Yes, I did an offline upgrade. 1. Stop all clients using gluster servers. 2. Stop glusterfsd and glusterd on both servers. 3. Backed up /var/lib/gluster* in all servers just to be safe. 4. Upgraded all servers from 3.6.x to 3.10.x (I did not have quotas or anything that required special steps) 5. Started gluster daemons again and confirmed everything was fine prior to letting clients connect. 5.

Hi Diego, Just to clarify, so did you do an offline upgrade with an existing cluster (3.6.x => 3.10.x)? Thanks. On Fri, Aug 25, 2017 at 8:42 PM, Diego Remolina <dijuremo at gmail.com> wrote: > I was never able to go from 3.6.x to 3.7.x without downtime. Then > 3.7.x did not work well for me, so I stuck with 3.6.x until recently. > I went from 3.6.x to 3.10.x but downtime was

On Tue, Jul 11, 2017 at 5:12 PM, Diego Remolina <dijuremo at gmail.com> wrote: > > > > You should first upgrade servers and then clients. New servers can > > understand old clients, but it is not easy for old servers to understand > new > > clients in case it started doing something new. > > But isn't that the reason op-version exists? So that regardless

Well it was probably caused by running replica 2 and doing online upgrade. However I added brick, turned volume to replica 3 with arbiter and got very strange issue I will mail to this list in a moment... Thanks. -ps On Tue, Jul 11, 2017 at 1:55 PM, Pranith Kumar Karampuri <pkarampu at redhat.com> wrote: > > > On Tue, Jul 11, 2017 at 5:12 PM, Diego Remolina <dijuremo at

OK, so killall seems to be ok after several attempts i.e. iops do not stop on VM. Reboot caused I/O errors after maybe 20 seconds since issuing the command. I will check the servers console during reboot to see if the VM errors appear just after the power cycle and will try to crash the VM after killall again... -ps On Fri, Sep 8, 2017 at 12:57 PM, Diego Remolina <dijuremo at gmail.com>

Gandalf, SIGKILL (killall -9 glusterfsd) did not stop I/O after few minutes. SIGTERM on the other hand causes crash, but this time it is not read-only remount, but around 10 IOPS tops and 2 IOPS on average. -ps On Fri, Sep 8, 2017 at 1:56 PM, Diego Remolina <dijuremo at gmail.com> wrote: > I currently only have a Windows 2012 R2 server VM in testing on top of > the gluster storage,

Good point Diego. Thanks! On Thu, Sep 21, 2017 at 9:49 AM, Diego Remolina <dijuremo at gmail.com> wrote: > Not so fast, 3.8.4 is the latest if you are using official RHEL rpms > from Red Hat Gluster Storage, so support for that should go through > your Red Hat subscription. If you are using the community packages, > then yes, you want to update to a more current version. >