[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-nfs
Subject:    Re: fsx size error (was: File Read Returns Non-existent Null Bytes)
From:       Trond Myklebust <trond.myklebust () primarydata ! com>
Date:       2015-02-26 23:06:43
Message-ID: CAHQdGtTibveUPBVD1n_4zMSRfGS2FAt3_oNfUdZjH=uvzXL-Yg () mail ! gmail ! com
[Download RAW message or body]

On Thu, Feb 26, 2015 at 2:00 PM, Chuck Lever <chuck.lever@oracle.com> wrote:
>> The alternative would be to add a "barrier" operation to allow the
>> setattr code to wait for all RPC calls before ours to complete (it
>> would have to wait not just for READ, but also GETATTR and all other
>> operations to the file). We could do that too.
>
> Yes. A barrier is usually heavyweight, though. And I thought there
> was some exclusion between GETATTR and SETATTR, so forcing an
> inode revalidation should work too? Or would that result in an
> unneeded data cache invalidation?
>

I found a better solution, I think. Please see the 5 patches I just sent out.

-- 
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@primarydata.com
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]