similar to: Slow performance with cifs client

Hi there, at first, the following scenario is used in our environment: Server-Side: - One Samba PDC using 3.0.24 release with TDB-backend. - Some Samba member servers serving files, home-dirs, etc. Client-Side: - Windows XP-Clients. - Windows Vista Clients (testing). - some Linux Ubuntu Distro (Feisty) Clients, using CIFS to access the samba-shares. fstab-entry of the Ubuntu-clients:

Hi, is there nobody in the community with the same problem or solution for the problem mentioned below? CU, Michael >From: "Mickey Smith" <speedcracker@hotmail.com> >To: samba@lists.samba.org >Subject: [Samba] Linux CIFS-access problem since samba 3.0.25(a/b) >Date: Thu, 12 Jul 2007 12:56:37 +0000 > >Hi there, > >at first, the following scenario is

I know this isn't the right place to ask this question, but does anybody know if it's possible to force a Linux client machine to spawn multiple cifsd's when connecting to a SINGLE Samba Server? I seem to be running into some Linux cifs client limits with a single connection. One cifs client can talk to multiple Samba servers at around 100 MB/sec (aggregate) over a single GigE

hi, guys: Today when i typed "mount " command on the server and found this message: .. ... 192.168.9.252: /home/share/tmp on /net/tmp/share type nfs ( rw, bg, soft,rsize=8192,wsize=8192,addr=192.168.9.252) 192.168.9.252: /home/share/tmp on /net/tmp/share type nfs ( rw, bg, soft,rsize=8192,wsize=8192,addr=192.168.9.252) 192.168.9.252: /home/share/tmp on /net/tmp/share type nfs (

I set up a 3.3 gluster volume for another sysadmin and he has added it to his cluster via automount. It seems to work initially but after some time (days) he is now regularly seeing this warning: "Too many levels of symbolic links" $ df: `/share/gl': Too many levels of symbolic links when he tries to traverse the mounted filesystems. I've been using gluster with static mounts

Hello all, I have observed a problem with a diskless PXE client I am attempting to configure. PXE/NFS/DHCP/TFTPd server is running CentOS5.1 and the Diskless workstation's root and kernel was extracted from a CentOS5.1 (custom kernel due to setting to enable Root File System support). Problem: When the diskless client boots and logs in I notice that my root user is being squashed, even if I

Also from my observation, based on network packets and time measurements, it seems the CIFS clients haven't done any sort of cache. For example, doing a "ls" for 5 times on the same folder within a short period of time. The network packet sizes are almost equal every time and the time it takes is similar. Isn't there supposed to be some page cache or dentry cache that could

Hi Samba users, We would like to use samba for re-exporting our other distributed file system (BeeGFS). However, we found that the meta data operations are very slow (dir stat, removal etc.). On SMB client the performance is more than 30x slow than on the SMB server. We would expect some slowness but this is too big a drop. This is the result on CIFS client $ sudo mdtest -b 10 -I 10 -L -z 2

I have this NFS client that used to be on Red Hat 7.3. For mounting user home directories I used this line in /etc/auto.master file: /home yp:auto.home rw,rsize=8192,wsize=8192 Moved the box to CentOS 4... The format of the file changed, so I attempted something like this: /home -rw,rsize=8192,wsize=8192 yp:auto.home No habla. Doesn't work. The rsize and wsize options seems to be

nfsmount doesnt work anymore for me. This patch fixes at least udp nfs mounts. tcp does still hang. client and server is 2.6. --- /dev/shm/bindresvport.c 2003-12-08 02:33:24.000000000 +0100 +++ klibc/inet/bindresvport.c 2004-01-06 21:05:02.283779072 +0100 @@ -23,7 +23,7 @@ int bindresvport(int sd, struct sockaddr if (sin == NULL) { sin = &me;

Hi all, I'm migrating from Gentoo to CentOS... I'm experiencing a rather low performance in NFS r/w (as client). NFS server is solaris (which exports zfs volumes via nfs). The very same exports were mounted with the same parameters (auto,nosuid,exec) on gentoo and centos server (bot x86_64)... It happens that centos is 5-10 times slower either in read and write operations... Ok,

Hello list, I'm using Samba 3.4.5 on a home-hosted fileserver of mine to easily share files with both GNU/Linux and Windows XP (Professional 32Bit SP3) clients. The machines are connected to each other via a switched GBit ethernet network, the actual available bandwidth between the server and the nodes over TCP amounts to about 940-980MBit (according to iperf). The server's storage

Hi, >>The same drive can be mounted and accessed easily with cifs://vienas01.andritz.com/HIPASE on /media/HIPASE_Q type cifs >>(rw,nosuid,nodev,relatime,vers=1.0,cache=strict,username=<snip>,domain=<snip>,uid=1000,forceuid,gid=1000,forcegid,addr=172.24.180.161,\ >>

In case anyone's interested, I followed up in the linux-nfs mailing list: https://marc.info/?l=linux-nfs&m=156887818618861&w=2 Thanks, Alkis On 9/15/19 10:51 AM, Alkis Georgopoulos wrote: > I think I got it. > > Both nfsmount and `mount -t nfs` now default to rsize/wsize = 1 MB. > By lowering this to 32K, all issues are gone, even with the default > timeo=7. And

Peter, we found that nfs over udp will corrupt data under very extrem load, there is no way to fix it due to the way how UDP works. TCP will not have these problems. I also wonder why the package size is only 1k. Everyone who wishes a slow connection can pass the desired options via the kernel cmdline. Everyone else prefers probably the fast mount. The defaults should look more like that: ---

I think I got it. Both nfsmount and `mount -t nfs` now default to rsize/wsize = 1 MB. By lowering this to 32K, all issues are gone, even with the default timeo=7. And nfsroot=xxx client responsiveness is a whole lot better. I think when nfsmount was initially written, the default rsize/wsize were much lower, which matched the timeo=7. Now they cause the lags/timeouts that I reported. So

Hello I have a problem with Invalid data System debian10 dovecot-2.2.36.4 # 2.2.36.4 (baf9232c1): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24.rc1 (debaa297) # OS: Linux 4.19.0-12-amd64 x86_64 Debian 10 Oct 23 15:57:52 dovecot6 dovecot: lmtp(33973,media4_js,2KEXD2Dhkl+1hAAAe3x6RQ): Error: Broken file /vmail/me/media4_js/Maildir/dovecot-uidlist line 6875: Invalid data: In debian9 -

Hello, i'm using version 4.07. On my computer extlinux does not work. after debugging, i found the trouble. in the function parse_mountinfo there was using a function get_string. in the function get_string there was a line (42) } else if (ch == '\\') { but in my mountinfo list, there was \ , but not with octal digit. so the function get_string will fail. here are some information

I have a system that I'm vetting as a NAS server. It has a 2.0TB XFS filesystem mounted on /storage and I'm doing benchmarks using nfs3, nfs4, and samba. I'm testing via iozone by mounting the filesystem from my "nas client" box and then running iozone on the mounted filesystem. NFS seems pretty fast - ie, several orders of magnitude faster than samba, and I'm

We have a Xen 3.0 / Linux kernel 2.6.15 machine with the domU''s configured for shared /home directories. One of the domU''s is an NFS server, exporting /home, and the other domU''s all mount this. It all functions fine, but it''s pretty slow. I tried untarring a recent Linux kernel tarball. On the NFS server domU this takes about 25 seconds. I didn''t