Hi.
Well, you are perfectly right, and it actually is an issue... For performance reasons, I try to cache data in memory (directory contents and file characteristics), and only go back to actually reading the disk only when needed.
The problem is that I consider that the disk has changed only when some internal VMS structure (namely the Volume Lock Value Block) has changed. As some of you may have witnessed, this gives really a lot of enhancements...
Unfortunately, this data changes only when there is either allocation or deallocation on the volume, so if you just rename a file from outside your Samba session, the number of free blocks does not change, so it's not seen in your session before someone either creates or deletes something (changes the number of free blocks on the volume, anyway), or if you do something within your Samba session that forces to invalidate the caches (such as renaming something, creating or deleting a file, ...).
I don't know what I can do about that, except removing the memory caching (and then multiply the browsing time by may be 30 or 40)...
JY Collot
-----Message d'origine-----
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Envoyé : lundi 24 février 2003 17:11
À : [EMAIL PROTECTED]
Objet : Problem file lookup on 2.2.7a Alpha
Hi evereybody,
I successfully installed Samba 2.2.7a on an AlphaServer GS140 running OpenVMS
7.2-2
All things I've tested look fine, except one problem :
First I connect my homeshare. Looks great, I can see all my files.
Then, I rename a file on OpenVMS for example $ RENAME TEST.TXT TEST1.TXT
Then I refresh the view from the Windows explorer and nothing changes.
No new file test1.txt appears. Instead I still see a file named test.txt.
When I now try to open this file, a message says, that this file can not be
found.
Can anyone reproduce this problem ? or do I have to change some options ?!?!
Have a nice day
Martin Philippi
