Frank Filz

I just added some text to the wiki documentation for FSAL_VFS.

Could you give more insight on this question?

Really the best solution is that client option since the issue is a client side limitation.

The state parameter points to a state_t that describes the state for the operation. The FSAL may/probably has an extension over what is used at the protocol layer (9p/NFSv3/NFSv4). Some...

If we push locks into the back end, the back end needs to be able to treat each NFS lock owner as a separate lock owner. This requires SOMETHING that...

While there may be a consideration that is helpful to the FSAL to use the full lockowner, note that then the FSAL would need to use that full lock owner...

Hmm, I'd have to think about this. We haven't really addressed lock fairness and there is a question how much energy to put into NFSv3. What does GPFS itself do...

Ganesha does have the xattr support from NFSv4.2 and FSAL_CEPH is hooked up to use it.

They were added in V4-dev.55, looks like a bunch of patches.

Closing for being inactive for more than 60 days. Please re-open if you have more questions.