On Fri, 28 Jan 2022, J. Bruce Fields wrote: > On Fri, Jan 28, 2022 at 09:41:24AM +1100, NeilBrown wrote: > > It's complicated.... > > > > The customer has an HA config with multiple filesystem resource which > > they want to be able to migrate independently. I don't think we really > > support that, but they seem to want to see if they can make it work (and > > it should be noted that I talk to an L2 support technician who talks to > > the customer representative, so I might be getting the full story). > > > > Customer reported that even after unexporting a filesystem, they cannot > > then unmount it. Whether or not we think that independent filesystem > > resources is supportable, I do think that the customer should have a > > clear path for unmounting a filesystem without interfering with service > > provided from other filesystems. Stopping nfsd would interfere with > > that service by forcing a grace-period on all filesystems. > > The RFC explicitly supports admin-revocation of state, and that would > > address this specific need, so it seemed completely appropriate to > > provide it. > > I was little worried that might be the use-case. > > :-) > I don't see how it's going to work. You've got clients that hold locks > an opens on the unexported filesystem. So maybe you can use an NFSv4 > referral to point them to the new server. Are they going to try to > issue reclaims to the new server? There's more to do before this works. As I hope I implied, I'm not at all sure that the specific problem that the customer raised (cannot unmount a filesystem) directly related to the general solution that the customer is trying to create. Some customers like us to hold their hand the whole way, others like to (feel that they) have more control. In general I like to encourage independence (but I have to consciously avoid trusting the results). We have an "unlock_filesystem" interface. I want it to work for NFSv4. The HA config was background, not a complete motivation. > > > As an aside ... I'd like to be able to suggest that the customer use > > network namespaces for the different filesystem resources. Each could > > be in its own namespace and managed independently. > > Yeah. Then you're basically migrating the whole server, not just the > one export, and that's more of a solved problem. Exactly. > > > However I don't think we have good admin infrastructure for that do > > we? > > > > I'd like to be able to say "set up these 2 or 3 config files and run > > systemctl start nfs-server@foo and the 'foo' network namespace will be > > created, configured, and have an nfs server running". Do we have > > anything approaching that? Even a HOWTO ?? > > But I don't think we've got anything that simple yet? I guess I have some work to do.... Thanks, NeilBrown
