Re: [fuse-devel] Allow read/write/flush/fsync of unlinked files when FUSE_HARD_REMOVE is set.

[Miklos S. <mi...@sz...>]

> For each file, I open a duplicate. Sometimes the duplicate doesn't get 
> opened immediately. If all of a sudden the duplicate can be opened, and 
> the original file was deleted, I can ignore it instead of re-opening the 
> duplicate. If I was to not use hard_remove, I could look for 
> ".fuse_hidden" in the file-name instead of "-".

I'm not sure I understand.  Is it the case that you perform every
operation on two files instead of just one?  

> OK. Maybe the hard_remove option shouldn't be available?

Yes, that sounds like a good solution.  Or just make a very strong
warning in the README against it's use.

> So, in addition to the problems out-lined in my previous e-mail, without 
> my patch, the following are true when hard_remove is set:
> 
> On unlinked files:
> - read() doesn't work,
> - write() doesn't work,
> - fsync() doesn't work,
> - close() returns -1 and sets errno to ENOENT when there wasn't really a 
> problem.

Yes, this is how it's supposed to work.  This option basically means,
that after removing an open file, everything will stop working.  The
release() method is the only exception, because I felt, that always
guaranteeing an open()/release() pair is important enough.

Miklos