On 25 Sep 2011, at 07:27, Troy Benjegerdes <[email protected]> wrote:

> So I figured once I found out how to make fuse work, and there was already a 
> testsuite, I should add something, so here goes.

Cool. Would you mind uploading this to gerrit? It would also make things much 
easier if you were prepared to license these files under a BSD-style license - 
at the moment, the copyright information refers to a file that isn't within the 
patch set, and we are very keen on avoiding a proliferation of different 
license texts within the codebase.

>  which requires me to at least be
> able to perform 'fs' commands through the fuse interface. 
> 
> I saw some mention of maybe using xattrs to do this...

To perform fs commands, there needs to be a way of issuing path ioctls to the 
cache manager. On Linux this is already done by using ioctls against a 
"special" file in /proc. For my money, the easiest way of doing this for fuse 
would be to also allow a special file that lives within the AFS namespace, and 
issue ioctls on that. Then, fs just needs a command line switch to say which 
AFS root it should be targeting.

> would this make the most
> sense? Would xattrs also be usefull in providing some information to a user
> (or just userspace) on the status of connected/disconnected/uploading a file?

My preferred mechanism for issuing reconnection status reports to the user 
would be to adapt the system that is already used to provide cache manager 
debugging information through fstrace. This supports the idea of collections, 
so you would simply define a disconnected state collection. You've then got a 
kernel to user space event logging infrastructure which could be easily 
harnessed by the fs command to report on which files are being resync'd, and 
how many more there are to go.

If you are interested in implementing any of this, let me know, and I'll be 
happy to point you in the right direction.

Cheers,

Simon
> 
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel

Reply via email to