On Wed, 2009-07-15 at 13:27 -0400, J. Bruce Fields wrote: [snip] > The mount options aren't really in the protocol--so it'd probably take > the form of a filesystem-granularity attribute that the client could > query (and then fail the mount if the client didn't like the answer). > > But even then: the fact is that someone will want to update the > filesystem some day. And there's no way to force every client > administrator to remount. So we'd have to decide how to handle that > case. So currently this is the case but at the last IETF meeting I proposed a remount callback to handle the case of a mass file relabel on the server. I think Beepy wrote it down on the possible 4.2 items. However I wouldn't expect to see anything related to that for a while and that assumes that someone picks up the ball and runs with it to begin with. Dave P.S. Note this is NFSv4 we are talking about I don't have a solution for v2(does anyone even use it any more?) or v3 -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
