search for: cifs_min_small

Displaying 8 results from an estimated 8 matches for "cifs_min_small".

2007 Sep 23
1
CentOS 5.0 crash (cifs bug ?)
...2.6.18-8.1.10.el5.centos.plus SMP mod_unload 686 REGPARM 4KSTACKS gcc-4.1 parm: 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.1...
2009 Jan 28
3
mount.cifs is not working (smbclient does work), somekind of recursive content in mount-dir
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
2011 Oct 07
3
SMB Signing issues... smbclient works, mount does not...
...vermagic: 2.6.18-274.3.1.el5 SMP mod_unload 686 REGPARM 4KSTACKS gcc-4.1 parm: 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...
2009 Jan 29
6
mv errors.
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
2015 May 17
0
Cifs mount / CIFS error
...vermagic: 2.6.32-504.16.2.el6.x86_64 SMP mod_unload modversions parm: 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...
2012 Feb 03
1
Samba 3.5 & CIFS mounts - long standing issue...
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
2011 Oct 26
0
mount.cifs - 4.8.1 -- server side restart - CIFS VFS: No repsonse for cmd
...5 depends: vermagic: 2.6.32-131.6.1.el6.x86_64 SMP mod_unload modversions parm: 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&...
2008 Apr 10
4
File locks?
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