On Fri, Sep 22, 2023 at 5:07 PM Trond Myklebust <trondmy@xxxxxxxxxxxxxxx> wrote: > > On Fri, 2023-09-22 at 17:00 -0400, Olga Kornievskaia wrote: > > On Fri, Sep 22, 2023 at 3:05 PM Trond Myklebust > > > > > > Oh crap... Yes, that is a bug. Can you please apply the attached > > > patch > > > on top of the original, and see if that fixes the problem? > > > > I can't consistently reproduce the problem. Out of several xfstests > > runs a couple got stuck in that state. So when I apply that patch and > > run, I can't tell if i'm no longer hitting or if I'm just not hitting > > the right condition. > > > > Given I don't exactly know what's caused it I'm trying to find > > something I can hit consistently. Any ideas? I mean this stack trace > > seems to imply a recovery open but I'm not doing any server reboots > > or > > connection drops. > > > > > > > If I'm right about the root cause, then just turning off delegations on > the server, setting up a NFS swap partition and then running some > ordinary file open/close workload against the exact same server would > probably suffice to trigger your stack trace 100% reliably. Getting back to this now. Thanks for v2 and I'll test. But I'm still unclear, is there a requirement that delegations have to be off for when the client has NFS over swap enabled? I always run with delegations on in ONTAP and run xfstests. I don't usually run with NFS over swap enabled but sometimes I do. So what should be the expectations? If I choose this kernel configuration, then deadlock is possible? > > I'll see if I can find time to test it over the weekend. > > -- > Trond Myklebust > Linux NFS client maintainer, Hammerspace > trond.myklebust@xxxxxxxxxxxxxxx > >
