Re: pNFS layout, ROC and multiple opens

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Mar 27, 2015 at 10:33 AM, Mkrtchyan, Tigran
<tigran.mkrtchyan@xxxxxxx> wrote:
> which means that even I I set roc flag, I still need to recall layout.

No. It means that the layout is automatically returned on last close
and/or delegreturn. If you want it returned earlier then you need to
send a cb_layoutrecall.

> ----- Original Message -----
>> From: "Trond Myklebust" <trond.myklebust@xxxxxxxxxxxxxxx>
>> To: "Mkrtchyan, Tigran" <tigran.mkrtchyan@xxxxxxx>
>> Cc: "linux-nfs list" <linux-nfs@xxxxxxxxxxxxxxx>
>> Sent: Friday, March 27, 2015 3:08:39 PM
>> Subject: Re: pNFS layout, ROC and multiple opens
>
>> On Fri, Mar 27, 2015 at 7:24 AM, Mkrtchyan, Tigran
>> <tigran.mkrtchyan@xxxxxxx> wrote:
>>>
>>>
>>> Hi folks,
>>>
>>> we run into following issue:
>>>
>>> on a client host we have two processes - A and B.
>>> Process A opens a file and reads some data:
>>>
>>> OPEN -> LAYOUTGET -> READ.
>>> Notice, that layout has a roc set to true.
>>>
>>> Process B opens the same file:
>>>
>>> OPEN -> READ.
>>>
>>> Client obviously re-used layout information.
>>> Now, process A closes the file and as a result,
>>> layout becomes invalid.
>>
>> No it doesn't. See the errata.
>>
>> Cheers
>>   Trond



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




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux