We have a FAS3050 CF pair for home directory access via both NFS and CIFS. We use unix style file security throughout. We are running DOT 7.0.1R1.

We have discovered a directory with files apparently created via CIFS where the ctimes are almost two months in the future (Dec 30, 2005).

I am pretty sure that there is no way to muck with ctime via NFS. You can only set atime and mtime to arbitrary values and I think that the filer sets ctime based on its own clock.

Does CIFS work differently? Can you set ctime to something arbitrary with CIFS? Is there an option to prevent this?

We have some home grown backup software that access the filers via NFS that uses mtime and ctime to decide what files need to be backed up. If CIFS can set ctime arbitrarily, then our incremental dumps may be skipping files that should really be backed up.

Steve Losen scl@virginia.edu phone: 434-924-0640

University of Virginia ITC Unix Support