search

clintonjade / macfuse

Automatically exported from code.google.com/p/macfuse
Other
0 stars 0 forks source link

If open file, then change file remotely, then re-open file, opens the PREVIOUS version of file. #249

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Mount volume.
2. Open file.
3. Close file.
4. Edit & save file remotely (ie from machine that the file is actually on)
5. Re-open file.

What is the expected output? What do you see instead?

Expect to see new version of file, see previous version (step 2) instead.

What version of the product are you using? On what operating system?

Mac OS 10.4.10

SSHFS version 1.7 (MacFUSE, 10, May 4 2007, 15:04:35)
FUSE library version: 2.6.5
MacFUSE version 0.4.0
using FUSE kernel interface version 7.8

Please provide any additional information below.

Original issue reported on code.google.com by apinstei...@gtempaccount.com on 31 Jul 2007 at 3:38

GoogleCodeExporter commented 8 years ago 
Oopss.. RTFFAQ problem. The "-o nocaches" FAQ entry worked.

However, I'd still point out that maybe the caches should be OFF by default 
since
this problem is common enough to warrant an FAQ issue. 

Due to the limitations of the cache being able to detect changes, I'd argue that
turning ON caches should be an optimization that people who don't remote change
detection could do for performance.

Original comment by apinstei...@gtempaccount.com on 31 Jul 2007 at 3:48

GoogleCodeExporter commented 8 years ago 
Your expectation/understanding of "remote change detection" (there's no such 
thing in MacFUSE to begin with) is 
incorrect. If you're interested in learning more about this, I suggest you 
search both here (past issues) and on 
the macfuse-devel forum.

Original comment by si...@gmail.com on 31 Jul 2007 at 4:51

GoogleCodeExporter commented 8 years ago 
I did read about it on the FAQ. I also searched the issues DB (just now) but 
didn't find anything related to this 
bug. Do you have bug #'s I can look at? I'd be happy to educate myself more to 
have a more enlightened 
conversation.

I do basically understand that MacFUSE can't detect remote changes. This is 
exactly my point, and why I 
suggest to make nocache the default.

People using a filesystem expect that if they open a file they get the latest 
copy. So I am just suggesting to 
make that behavior the default behavior by not caching anything. For people 
that understand FUSE and sshfs 
enough to realize that things aren't cached and can't be detected but want more 
speed, then they could turn 
on caching themselves.

My main point simply being that it behaves in an unexpected way as configured 
by default, and that could be 
fixed, which would reduce confusion and be more consistent with expected 
filesystem behavior.

Of course, I don't know what are other consequences of not caching are, so that 
could also be an issue.

Original comment by apinstei...@gtempaccount.com on 31 Jul 2007 at 5:55