Ka-Hing Cheung

I suspect the problem is that the application does not read the file sequentially. While catfs can stream from remote, if the application reads at offset n catfs does need...

currently catfs cannot work offline as it always reach out to the backing store for metadata

looks like there's already a pipe but it's closed before control is returned to the application. Possibly just need an option to not close the pipe

The use case is the parent want to wait for the child to potentially show errors to the user. I currently use signals as you can see in https://github.com/kahing/goofys/commit/eb7963e9fb33235d5650ee0f634902cffdded573 ....

right now seems like you can put in any language, and the server would still import the correct one

what's the motivation of this? things like rename will still mess things up anyway

What is this filesystem scanner trying to ascertain by looking at the inode number? So this PR creates a "strange" side-effect: 1. `rm a && touch a` the inode number...

what do you think about the approach suggested in https://github.com/kahing/goofys/issues/419 ? From my perspective both of these asks are valid but also strange, and I'd rather have one strange way...

playing devil's advocate a bit: why would #419 have the same problem with access order? it would be base on etags which would stay the same it's not clear if...

I don't understand why a cache is needed, could you not hash(etag) instead of hash(filename) like this PR?