Anyone know why DOT updates the modification time on a ntfs folder when a file in that folder is simply opened? This is not the way it works on our other NT systems. Is this a "feature", a bug, or just a difference between ntfs and wafl's interpretation of ntfs? I'm on a F880c running 6.3.1R1....and I'm a unix person so I may be missing the obvious, but I don't think so. Thanks,
______________________________________________________________ Jeff Burton Storage Architect Abbott Laboratories EMAIL: Jeffrey.Burton@Abbott.com Dept. GB16/Bldg. AP14B-1 PHONE: 847-935-5778 100 Abbott Park Rd. FAX: 847-938-5824 Abbott Park, IL 60064-6042
Anyone know why DOT updates the modification time on a ntfs folder when a file in that folder is simply opened? This is not the way it works on our other NT systems. Is this a "feature", a bug, or just a difference between ntfs and wafl's interpretation of ntfs? I'm on a F880c running 6.3.1R1....and I'm a unix person so I may be missing the obvious, but I don't think so. Thanks,
Jeff Burton Storage Architect Abbott Laboratories EMAIL: Jeffrey.Burton@Abbott.com Dept. GB16/Bldg. AP14B-1 PHONE: 847-935-5778 100 Abbott Park Rd. FAX: 847-938-5824 Abbott Park, IL 60064-6042
My guess is that the application is doing more than a simple file open. Perhaps it is an editor that is creating a .bak file or something like that. As far as I know, to change the mod time of a directory (folder) you need to create, delete, or rename a file in the directory. Simply reading or writing an existing file does not change the directory mod time. An application could also explicitly set the mod time of the directory.
I can think of one other possibility, but I have doubts since this is a NTFS volume. If you create a directory with NFS, then it is not in unicode format (unless you specify an option to change this). The first time you access the directory via CIFS, it is converted to unicode, and this might also trip the directory mod time, but I don't know. Of course, this only happens once at the first CIFS access.
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support
As many of you expected the Word .doc file on the netapp was creating a tmp file which update the folder modification time. The Word .doc file used on the Windows NT system that did not update the modification time of the folder was not creating a tmp file in that folder. I'm guessing there is some setting in the Word doc or in a user Word profile that states if to create tmp files and where to create them. When the same exact file used on the NetApp was used on the local NT system it did update the modification time of the folder. I knew it was something obvious. Oh well, thanks all.
Jeff
On Wed, May 21, 2003 at 05:29:58PM -0400, Steve Losen wrote:
Anyone know why DOT updates the modification time on a ntfs folder when a file in that folder is simply opened? This is not the way it works on our other NT systems. Is this a "feature", a bug, or just a difference between ntfs and wafl's interpretation of ntfs? I'm on a F880c running 6.3.1R1....and I'm a unix person so I may be missing the obvious, but I don't think so. Thanks,
Jeff Burton Storage Architect Abbott Laboratories EMAIL: Jeffrey.Burton@Abbott.com Dept. GB16/Bldg. AP14B-1 PHONE: 847-935-5778 100 Abbott Park Rd. FAX: 847-938-5824 Abbott Park, IL 60064-6042
My guess is that the application is doing more than a simple file open. Perhaps it is an editor that is creating a .bak file or something like that. As far as I know, to change the mod time of a directory (folder) you need to create, delete, or rename a file in the directory. Simply reading or writing an existing file does not change the directory mod time. An application could also explicitly set the mod time of the directory.
I can think of one other possibility, but I have doubts since this is a NTFS volume. If you create a directory with NFS, then it is not in unicode format (unless you specify an option to change this). The first time you access the directory via CIFS, it is converted to unicode, and this might also trip the directory mod time, but I don't know. Of course, this only happens once at the first CIFS access.
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support
On Wed, May 21, 2003 at 05:29:58PM -0400, Steve Losen wrote:
My guess is that the application is doing more than a simple file open. Perhaps it is an editor that is creating a .bak file or something like that.
I know of at least one editor that runs on Windows that does something like that - it creates a temporary file, does its writes to the temporary file, and then, if you save your work, it renames the temporary file to the regular file name, presumably so that you don't lose your work if a write to the temporary file fails.
The executable image for that editor has the name "WINWORD.EXE". People have been known to run that on Windows every once in a while. :-)
Given that, I'd expect running Word on a document to change the mod time on the directory containing the file even on NTFS - and, in fact, it did that when I tried it on a directory I created in C:\TEMP.
I can think of one other possibility, but I have doubts since this is a NTFS volume. If you create a directory with NFS, then it is not in unicode format (unless you specify an option to change this). The first time you access the directory via CIFS, it is converted to unicode, and this might also trip the directory mod time, but I don't know.
No, it just changes the inode change time; that's sufficient to cause it to be dumped by "dump".
-
Guy Harris -
Jeff Burton -
Steve Losen