Chuck Ebbert wrote:
On 08/22/2007 11:18 AM, 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
>> > 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?
> Just curious... What are the differences in the mounts options that
> is causing this new check to pop, which in turn is failing the mount?
In at least one case it is read-only vs. read-write.
This should not make the
User mounts something from the server read-only, then mounts selected
exports from the same filesystem read-write on top of that.
The check looks for
difference protocols, I/O sizes, or cache timeouts
so there has to be something other ro/rw that is causing the
mounts to fail...