On 6/29/07, Wojtek.Pilorz <wpilorz at bdk.pl> wrote: > On Fedora6, I have noted the folowing problems when using cifs to connect to > NT shares: > > - cp -vip does not copy mtime; tar x does copy mtime > (it seems setting modtime by fname does work, setting by handle does not) > - when there is a share mounted from a NT/2000 server which is not used for long time > mounting another share from the same servers reliably fails ; > touching the already mounted share (ls is OK) allows the mount so succeed. > - when using vim to edit a file on the share and trying to write it, vim often > says that the file has been modified in the meantime > - perhaps most annoying: somtimes modifying a file located on NT 4 Workstation share with vim, > it becomes permanently unavailable until NT is rebooted. > It happens rarely, I do not know how to trigger it on demand. > > Those problems did not happen when using smbfs from CentOS 4.4. > > I am wondering if CentOS 5 has these problems? > Anyone using cifs from CentOS 5 to access NT-exported share, would care to comment? > > Thanks, > > Wojtek I believe some of the issues you mentioned have been addressed in newer versions of cifs. For example, the vim/timestamp problem was reported and has been fixed in recent kernels. See: http://lists.samba.org/archive/linux-cifs-client/2007-June/002014.html However the CentOS kernel (2.6.18) uses cifs 1.45 and the current FC6 kernel (2.6.20) probably has cifs 1.47. Unless upstream/RH backports patches in their kernel, CentOS will not get them. One could compile cifs.ko from the source as a possible solution. If the problem is a severe one, it will be worth doing it. Akemi