question about CIFS client glitches
Subsystems (2)
Hello,
Trying out a CIFS mount of a W2K8 x64 file system from CentOS 5.5 and running into problems, and trying to figure out how to proceed.
I mount up the Windows share, then run a script that expands about ten TAR format archives containing a couple of hundred files with the 'pax' utility. Then it removes about two dozen files. The script is a primitive source-code version extractor.
Unfortunately the resulting tree is quite incorrect. Some of the files that should be deleted by the 'rm' commands are not, and some of the files that should be there from the expansion are missing. The script works fine with EXT2/3/4 and NFSv3 mounts.
So it seems to me CIFS mounts are not ready for use in production or development.
Before I give up, is there anything obvious that I'm missing? I searched for relevant bugs in Red Hat, Samba and Kernel.org bugzillas and didn't find anything that seems to match.
The version mix in use is a little odd. The kernel and 'cifs.ko' modules are pure RHEL/CentOS version 2.6.18-194.11.3.el5, but instead of using the distro version of Samba the system is running vanilla Samba 3.5.2.
If anyone has any ideas or suggestions, please let me know.
Thanks
A message that is not in the archive (sent off-list or not yet received): 6.2.5.6.2.20100916171408.03a0fcd8-8QzAbx0zao2B+jHODAdFcQ@public.gmane.org
Quoted 3 lines · At 05:39 PM 9/16/2010 -0400, starlight-Utvwg/[email protected]…
Trying out a CIFS mount of a W2K8 x64 file system from CentOS 5.5 and running into problems, and trying to figure out how to proceed.
Oops. I see the problem is that CIFS, at least in the older stable versions, does not support hard links. The extracted archives have a few of these and so the resulting tree is not a synchronized copy of the original.
Oh well, so much for that.
A message that is not in the archive (sent off-list or not yet received): 6.2.5.6.2.20100916184734.03a0f900-Utvwg/[email protected]
Quoted 5 lines · On Thu, 16 Sep 2010 18:49:49 -0400 starlight-Utvwg/[email protected]…
Quoted 3 lines · At 05:39 PM 9/16/2010 -0400, starlight-Utvwg/[email protected]…
Trying out a CIFS mount of a W2K8 x64 file system from CentOS 5.5 and running into problems, and trying to figure out how to proceed.
Quoted 7 lines
Oops. I see the problem is that CIFS, at least in the older stable versions, does not support hard links. The extracted archives have a few of these and so the resulting tree is not a synchronized copy of the original.
Oh well, so much for that.
Ok, good to know. There were patches that went to mainline to make CIFS support server inode numbers correctly, which is sort of a requirement for proper hardlink support. Those were really too invasive for a minor RHEL release however.
Signature · 1 line
Jeff Layton <[email protected]>
Quoted 19 lines · On Thu, Sep 16, 2010 at 4:39 PM, <starlight-Utvwg/[email protected]…
Hello,
Trying out a CIFS mount of a W2K8 x64 file system from CentOS 5.5 and running into problems, and trying to figure out how to proceed.
I mount up the Windows share, then run a script that expands about ten TAR format archives containing a couple of hundred files with the 'pax' utility. Then it removes about two dozen files. The script is a primitive source-code version extractor.
Unfortunately the resulting tree is quite incorrect. Some of the files that should be deleted by the 'rm' commands are not, and some of the files that should be there from the expansion are missing. The script works fine with EXT2/3/4 and NFSv3 mounts.
So it seems to me CIFS mounts are not ready for use in production or development.
Quoted 6 lines
Before I give up, is there anything obvious that I'm missing? I searched for relevant bugs in Red Hat, Samba and Kernel.org bugzillas and didn't find anything that seems to match.
The version mix in use is a little odd. The kernel and 'cifs.ko' modules are pure RHEL/CentOS version 2.6.18-194.11.3.el5,
This is quite old kernel, but perhaps it was updated to include more recent fixes - can you view the version information on the file, ie the cifs.ko module (you can do this by running modinfo on cifs.ko)
Signature · 3 lines
Thanks, Steve
A message that is not in the archive (sent off-list or not yet received): AANLkTimDWbZF=DkmVLw96V3nZGggFfNm0Zv3FxfFX1BE@mail.
gmail.com
Quoted 4 lines · Steve French
Quoted 3 lines · On Thu, Sep 16, 2010 at 4:39 PM, <starlight-Utvwg/[email protected]…
Trying out a CIFS mount of a W2K8 x64 file system from CentOS 5.5 and running into problems, and trying to figure out how to proceed.
...
Quoted 6 lines
This is quite old kernel, but perhaps it was updated to include more recent fixes - can you view the version information on the file, ie the cifs.ko module (you can do this by running modinfo on cifs.ko)
Thank you for the follow-up. Per my last message this was my being a clueless in regards to the lack of hard/soft link support in the old version. 'modinfo' pegs it as 1.60RH.
Hopefully RHEL6 will include CIFS file links as it might work better to compile on Linux from a Windows share rather than vice-versa. 'makedepend' runs painfully slow from Windows over a Samba share unless IPoIB is used for transport.
Perhaps I'll try it under Fedora, though in general I find wrestling with the constant change of the moving-target distro too much.
It is quite encouraging to see CIFS work in general. Last time I tried three or four years ago the system crashed shortly after issuing the mount command.
A message that is not in the archive (sent off-list or not yet received): 6.2.5.6.2.20100916195402.0573dcc0-Utvwg/[email protected]
Quoted 22 lines · On Thu, Sep 16, 2010 at 7:00 PM, <starlight-Utvwg/[email protected]…
Quoted 4 lines · Steve French
Quoted 3 lines · On Thu, Sep 16, 2010 at 4:39 PM, <starlight-Utvwg/[email protected]…
Trying out a CIFS mount of a W2K8 x64 file system from CentOS 5.5 and running into problems, and trying to figure out how to proceed.
...
Quoted 6 lines
This is quite old kernel, but perhaps it was updated to include more recent fixes - can you view the version information on the file, ie the cifs.ko module (you can do this by running modinfo on cifs.ko)
Thank you for the follow-up. Per my last message this was my being a clueless in regards to the lack of hard/soft link support in the old version. 'modinfo' pegs it as 1.60RH.
Hopefully RHEL6 will include CIFS file links as it might work better to compile on Linux from a Windows share rather than vice-versa. 'makedepend' runs painfully slow from Windows over a Samba share unless IPoIB is used for transport.
Quoted 5 lines
Perhaps I'll try it under Fedora, though in general I find wrestling with the constant change of the moving-target distro too much.
It is quite encouraging to see CIFS work in general.
There is a lot of work going on :)
We (Jeff, Suresh, Shirish, Pavel and I and others) are doing over 200 changesets a year fixing/improving the cifs kernel module (and hopefully will have a stable smb2 protocol kernel module for you next year).
Signature · 3 lines
Thanks, Steve
Quoted 22 lines · On Thu, 16 Sep 2010 20:00:14 -0400 starlight-Utvwg/[email protected]…
Quoted 4 lines · Steve French
Quoted 3 lines · On Thu, Sep 16, 2010 at 4:39 PM, <starlight-Utvwg/[email protected]…
Trying out a CIFS mount of a W2K8 x64 file system from CentOS 5.5 and running into problems, and trying to figure out how to proceed.
...
Quoted 6 lines
This is quite old kernel, but perhaps it was updated to include more recent fixes - can you view the version information on the file, ie the cifs.ko module (you can do this by running modinfo on cifs.ko)
Thank you for the follow-up. Per my last message this was my being a clueless in regards to the lack of hard/soft link support in the old version. 'modinfo' pegs it as 1.60RH.
Hopefully RHEL6 will include CIFS file links as it might work better to compile on Linux from a Windows share rather than vice-versa. 'makedepend' runs painfully slow from Windows over a Samba share unless IPoIB is used for transport.
Quoted 8 lines
Perhaps I'll try it under Fedora, though in general I find wrestling with the constant change of the moving-target distro too much.
It is quite encouraging to see CIFS work in general. Last time I tried three or four years ago the system crashed shortly after issuing the mount command.
RHEL6 is fairly current with mainline code (at least as of this past spring or so). If it works OK on Fedora, it should be OK in RHEL6.
Signature · 1 line
Jeff Layton <[email protected]>
Quoted 2 lines · Jeff Layton
RHEL6 is fairly current with mainline code (at least as of this past spring or so). If it works OK on Fedora, it should be OK in RHEL6.
Super. I'll try loading up the 6 beta in a VM and check it out.
Signature · 2 lines
To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Quoted 4 lines · Steve French
Quoted 3 lines · On Thu, Sep 16, 2010 at 4:39 PM, <[email protected]> wrote:
Trying out a CIFS mount of a W2K8 x64 file system from CentOS 5.5 and running into problems, and trying to figure out how to proceed.
...
Quoted 4 lines
This is quite old kernel, but perhaps it was updated to include more recent fixes - can you view the version information on the file, ie the cifs.ko module (you can do this by running modinfo on cifs.ko)
Tried the RHEL6 beta 2 and it behaves the same as RHEL 5.5. 'modinfo' output for both attached. 'cifs.ko' versions are 1.60RH and 1.63.
In both versions it seems like hard-links work and symbolic links fail with
ln: creating symbolic link `zzzz': Operation not supported
And it appears that a 'pax -r' extraction followed by 'rm' for selected files has some difficulty with CIFS 1.6x rendered hard link in the mix.
I'm probably giving up on the idea for now, but thanks for your help.
filename: /lib/modules/2.6.18-194.11.3.el5/kernel/fs/cifs/cifs.ko version: 1.60RH description: VFS to access servers complying with the SNIA CIFS Specification e.g. Samba and Windows license: GPL author: Steve French <[email protected]> srcversion: 20DD0BE6A19ED378F7D2C33 depends: vermagic: 2.6.18-194.11.3.el5 SMP mod_unload 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: 883f3504c7c19149bce751f598f18801122e6109d17621f882165893a79cb97d25e6869960ede5e09a2fef8da5b3ab56d24567891cdc21676f35835 filename: /lib/modules/2.6.32-44.2.el6.x86_64/kernel/fs/cifs/cifs.ko version: 1.63 description: VFS to access servers complying with the SNIA CIFS Specification e.g. Samba and Windows license: GPL author: Steve French <[email protected]> srcversion: 91CD42CFC5D35D5285E34E1 depends: vermagic: 2.6.32-44.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: 50 Range: 2 to 256 (int)
Signature · 2 lines
To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
A message that is not in the archive (sent off-list or not yet received): 6.2.5.6.2.20100917193123.056b6f78-Utvwg/[email protected]
Quoted 12 lines · On Fri, 17 Sep 2010 19:38:21 -0400 starlight-Utvwg/[email protected]…
Quoted 4 lines · Steve French
Quoted 3 lines · On Thu, Sep 16, 2010 at 4:39 PM, <starlight-Utvwg/[email protected]…
Trying out a CIFS mount of a W2K8 x64 file system from CentOS 5.5 and running into problems, and trying to figure out how to proceed.
...
Quoted 4 lines
This is quite old kernel, but perhaps it was updated to include more recent fixes - can you view the version information on the file, ie the cifs.ko module (you can do this by running modinfo on cifs.ko)
Quoted 9 lines
Tried the RHEL6 beta 2 and it behaves the same as RHEL 5.5. 'modinfo' output for both attached. 'cifs.ko' versions are 1.60RH and 1.63.
In both versions it seems like hard-links work and symbolic links fail with
ln: creating symbolic link `zzzz': Operation not supported
That's expected. The core cifs protocol as implemented in windows doesn't support symlinks. You need unix extensions for that, or you may want to play with the "mfsymlinks" patches that Metze proposed recently.
Quoted 6 lines
And it appears that a 'pax -r' extraction followed by 'rm' for selected files has some difficulty with CIFS 1.6x rendered hard link in the mix.
I'm probably giving up on the idea for now, but thanks for your help.
What sort of difficulty is it having?
Signature · 1 line
Jeff Layton <[email protected]>
Quoted 8 lines · Jeff Layton
Quoted 3 lines · On Fri, 17 Sep 2010 19:38:21 -0400 [email protected] wrote:
In both versions it seems like hard-links work and symbolic links fail
That's expected. The core cifs protocol as implemented in windows doesn't support symlinks.
Ah, well then it's a good thing they're not needed for the build tree I'm working with. Good to know not to ever look for the feature for Windows shares.
Quoted 3 lines
You need unix extensions for that, or you may
want to play with the "mfsymlinks" patches that Metze proposed recently.
Eeeh no. Every time I've ever worked with a vanilla kernel I sank in the quicksand of bugs and crashes. Not fun, no time for it.
Quoted 6 lines
Quoted 4 lines
And it appears that a 'pax -r' extraction followed by 'rm' for selected files has some difficulty with CIFS 1.6x rendered hard link in the mix.
What sort of difficulty is it having?
As expressed in the original message, 'pax' archive with hard links restored, 'rm' command executed, tree doesn't match. Maybe the fact that the 'pax' archive is created with a
find tree -print | sort -r | pax -wd
has something to do with it, causing the 'pax -r' to do things that CIFS is not expecting.
I am giving up though. Decided to build a new server and setup an IB link so that Samba works acceptably from Windows and the files can stay on the Linux side of the fence.
Signature · 2 lines
To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba