On Thu, Feb 17, 2022 at 06:27:15PM +0100, Richard Weinberger wrote: > > Von: "bfields" <bfields@xxxxxxxxxxxx> > > Thanks, I'll try to take a look. > > > > Before upstreaming, I would like us to pick just one. These kind of > > options tend to complicate testing and documentation and debugging. > > > > For an RFC, though, I think it makes sense, so I'm fine with keeping > > "reexport=" while we're still exploring the different options. And, > > hey, maybe we end up adding more than one after we've upstreamed the > > first one. > > Which one do you prefer? > "predefined-fsidnum" should be the safest one to start. I don't know! I'll have to do some more reading and think about it. > > Setting the timeout to 0 doesn't help with re-export server reboots. > > After a reboot is another case where we could end up in a situation > > where a client hands us a filehandle for a filesystem that isn't mounted > > yet. > > > > I think you want to keep a path with each entry in the database. When > > mountd gets a request for a filesystem it hasn't seen before, it stats > > that path, which should trigger the automounts. > > I have implemented that already. This feature is part of this series. :-) Oh, good, got it. It'll take me some time to catch up. --b.
