Linux NFS development
 help / color / mirror / Atom feed
From: marc eshel <eshel.marc@gmail.com>
To: Anna Schumaker <anna@nowheycreamery.com>,
	Olga Kornievskaia <aglo@umich.edu>,
	Trond Myklebust <trondmy@hammerspace.com>
Cc: linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: issues with Linux client pNFS
Date: Thu, 17 Sep 2026 12:00:09 -0700	[thread overview]
Message-ID: <0fc174bd-ec6b-45a6-be73-221d5b2b3518@gmail.com> (raw)
In-Reply-To: <f3218169-f309-477a-b439-3d106debd053@gmail.com>

Hi Anna,

Reading the code around this patch it looks like some other flags are 
checked, so I tried to add RCA4_TYPE_MASK_OTHER_LAYOUT_MAX and with this 
flags file layout recall did work.

Thanks, Marc.

On 9/17/26 8:42 AM, marc eshel wrote:
> Hi Anna,
>
> This fix is related to DELEGATION_RETURN only, I was trying to recall 
> all file layouts.
>
> Marc.
>
> On 9/17/26 6:29 AM, Anna Schumaker wrote:
>> Hi Marc,
>>
>> On Wed, Sep 16, 2026, at 6:30 PM, marc eshel wrote:
>>> Hi,
>>>
>>> I was just trying pNFS recall any but it look like the NFS client
>>> received but ignored the call, is that expected ?
>>>
>>> [287100.214040] NFS: RECALL_ANY callback request from 10.11.96.99
>>> [287100.214073] nfs4_callback_recallany: exit with status = 0
>> Trond just had a patch the other day to fix an issue with CB_RECALL_ANY.
>> Any chance you're able to test it to see if it fixes your issue?
>>
>> https://lore.kernel.org/linux-nfs/115e4102b1bab159c25e8e903070b55cc4de77eb.1789148631.git.trond.myklebust@hammerspace.com/ 
>>
>>
>> Thanks,
>> Anna
>>> Thanks, Marc.
>>>
>>> On 9/16/24 1:33 PM, Anna Schumaker wrote:
>>>> Hi Marc,
>>>>
>>>> On 9/16/24 4:27 PM, marc eshel wrote:
>>>>> Hi,
>>>>>
>>>>> Who is the current maintainer of the Linux NFS client?
>>>> That would be me and Trond.
>>>>
>>>>> I have an issue with the way pNFS client is distributing the reads 
>>>>> among the DSs and I can provide the traces if anyone cares.
>>>> What is the problem? And sure, send along the traces! I'll try to 
>>>> take a look as soon as I can.
>>>>
>>>> Anna
>>>>
>>>>> Thanks, Marc.
>>>>>

      reply	other threads:[~2026-09-17 19:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16 20:27 issues with Linux client pNFS marc eshel
2024-09-16 20:33 ` Anna Schumaker
2024-09-16 21:51   ` marc eshel
2026-09-16 22:30   ` marc eshel
2026-09-17 13:29     ` Anna Schumaker
2026-09-17 15:42       ` marc eshel
2026-09-17 19:00         ` marc eshel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0fc174bd-ec6b-45a6-be73-221d5b2b3518@gmail.com \
    --to=eshel.marc@gmail.com \
    --cc=aglo@umich.edu \
    --cc=anna@nowheycreamery.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@hammerspace.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox