On Tue, 2007-08-21 at 12:14 -0400, Steve Dickson wrote:
Dave Jones wrote:
> On Tue, Aug 21, 2007 at 10:29:53AM -0400, Chuck Ebbert wrote:
> > If people try mounting several exports from the same filesystem, it fails
> > with confusing error messages if the mount options are different for some
> > of the mount points. Adding "nosharecache" to the mount options
fixes that,
> > but people with working setups suddenly find they need this new option to
> > use a setup that used to work without it. Should we just revert that patch?
Thats been the million dollar question lately... there has been quite a
bit of complaints about this patch... but note the check does do some
correct sanity checking so the changes it point would be a good
thing to do....
But with that said, I would if making it a warning first, giving
people time to clean up their setups and then making it an
error later on...
steved.
It is important that people know about the consequences of using
nosharecache: namely that they may see cache corruption when accessing
the same file via different mountpoints. That is why I firmly believe it
should _NOT_ be a default.
Trond