On Sun, Nov 13, 2011 at 02:45:48PM +0100, Tigran Mkrtchyan wrote: > I have a server which runs on top of hadoop. The problem with hadoop > is that there is no way to have persistent file handles. I am > currently working on a way to do that - either simulate them or add a > support for unique file id to hadoop. If linux client will support > volatile file handles then I can stop inventing some workarounds. I might call that "fixing" rather than inventing workarounds. Our of curiosity: if we really wanted to support such filesystems, what would we need in the protocol? Just saying "filehandles aren't stable, deal with it" seems insufficient. Say there was some way for the client to indicate which filehandles it currently has in use, and some way for the server to ask the client to return in-use filehandles if there are too many (like DELEG_RECALL_ANY). Then the server could at least place a limit on the number of filehandles that it had to guarantee persistent. And/or the client could get a callback on rename/link/unlink. Bah. Would any of that actually be easier than implementing persistent file handles? --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
