search for: cifs_max_pending

...CIFSMaxBufSize:Network buffer size (not including header). Default: 16384 Range: 8192 to 130048 (int) parm: cifs_min_rcv:Network buffers in pool. Default: 4 Range: 1 to 64 (int) parm: cifs_min_small:Small network buffers in pool. Default: 30 Range: 2 to 256 (int) parm: cifs_max_pending:Simultaneous requests to server. Default: 50 Range: 2 to 256 (int) The cifs.ko is version 1.45 .... I think this is still the buggy version, right ??? I have two CentOS 5.0 boxes, both running 2.6.18-8.1.10.el5.centos.plus and using automounter to mount WinXP's share. I use this as part of...

Hi all, When I try to make a connection to our windows server with smbclient: smbclient //server/dira/dirb/dirc -U username -W workgroup Password: ***** I get a working ftp-like connection to our data. When I try to make the same connection with mount.cifs: mount.cifs //server/dira/dirb/dirc /mnt/mnt_dir -o user=877790 dom=workgroup Password: ***** I get a mount to a location which appears

...CIFSMaxBufSize:Network buffer size (not including header). Default: 16384 Range: 8192 to 130048 (int) parm: cifs_min_rcv:Network buffers in pool. Default: 4 Range: 1 to 64 (int) parm: cifs_min_small:Small network buffers in pool. Default: 30 Range: 2 to 256 (int) parm: cifs_max_pending:Simultaneous requests to server. Default: 50 Range: 2 to 256 (int) module_sig: 883f3504e66bf24104f42edc2b0f945112c79009d1e1918c363e6545d5644af26235486a0faee309e3e516f3731905cd551976d305e8c32b5f117ae9b This works without issues: smbclient -U username //192.168.20.129/share But this does not work...

I have Debian Etch with Samba. I windows clients I do not get any errors when move files to the /mnt/videos on the server. However n Linux clients I do get some errors. (Using rox-filer or the mv command-line). This are the errors: bash >>> mv post.txt share/ mv: preserving times for `share/post.txt': Invalid argument mv: setting permissions for `share/post.txt': No such file or

...CIFSMaxBufSize:Network buffer size (not including header). Default: 16384 Range: 8192 to 130048 (int) parm: cifs_min_rcv:Network buffers in pool. Default: 4 Range: 1 to 64 (int) parm: cifs_min_small:Small network buffers in pool. Default: 30 Range: 2 to 256 (int) parm: cifs_max_pending:Simultaneous requests to server. Default: 32767 Range: 2 to 32767. (int) parm: enable_oplocks:Enable or disable oplocks (bool). Default:y/Y/1 (bool) [root at atgrzsl1282 tmp]# mount.cifs -V mount.cifs version: 4.8.1 TIA Micha

...e the aggregate throughput that I get if I connect all by CIFS. So, the bandwidth between the two machines has the potential to be much higher than what I get just by CIFS. And of course FTP and RSYNC without encryption shows almost line speed. I am experimenting with some of the CIFS tunables (cifs_max_pending and CIFSMaxBufSize). For various reasons, I have to mount with "directio" so wsize and rsize aren't really relevant. But it seems the easy way out might be to somehow get multiple cifsd processes talking to the same server. Is it possible? What if I give more than one IP Address...

Hi. I can see that this is a long long standing issue... Apparently things changed in Windows 2008 R2, and after upgrade of domain from R1 to R2 cifs mounts don't work anymore between Linux servers. Windows can see Samba shares and mount them, but CIFS on another Linux box cannot... Here is a thread with explanation in lenght: http://ubuntuforums.org/showthread.php?t=1178484 I get the

...CIFSMaxBufSize:Network buffer size (not including header). Default: 16384 Range: 8192 to 130048 (int) parm: cifs_min_rcv:Network buffers in pool. Default: 4 Range: 1 to 64 (int) parm: cifs_min_small:Small network buffers in pool. Default: 30 Range: 2 to 256 (int) parm: cifs_max_pending:Simultaneous requests to server. Default: 50 Range: 2 to 256 (int) Documentation for the Unisys Mainframe can be found here.... http://public.support.unisys.com/search/DocumentationSearch.aspx?ID=643&pla=ps&nav=ps Unisys MCP release 13.1 MCP: *SYSTEM/MCP/541_74 [MCP 13 / SSR 54.1 (54.189....

Hello, Recently, the following problem started happening with a particular samba server: If i have a file open for reading (say, a pdf in xpdf) and then try to write to it (say, through recompiling a latex document) it complains that it cannot open the file for writing. this seems like a file lock issue but I am unsure where it is happening. My previous usage should be perfectly safe since