From: Olga Kornievskaia <aglo@umich.edu>
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: "neilb@suse.com" <neilb@suse.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: multipath patches
Date: Thu, 11 Jul 2019 16:33:57 -0400 [thread overview]
Message-ID: <CAN-5tyG0jdyn8C11v6b8=v3d1p=WoMAhXrAw8mWGEUn-TVXJ=g@mail.gmail.com> (raw)
In-Reply-To: <1d019c416f69aa7f3ba7fed3bcfd4c08088fba57.camel@hammerspace.com>
On Thu, Jul 11, 2019 at 3:29 PM Trond Myklebust <trondmy@hammerspace.com> wrote:
>
> On Thu, 2019-07-11 at 15:06 -0400, Olga Kornievskaia wrote:
> > Hi Trond,
> >
> > I see that you have nconnect patches in your testing branch (as well
> > as your linux-next and I assume they are the same). There is
> > something wrong with that version. A mount hangs the machine.
> >
> > [ 132.143379] watchdog: BUG: soft lockup - CPU#0 stuck for 23s!
> > [mount.nfs:2624]
> >
> > I don't have such problems with the patch series that Neil has
> > posted.
> >
> > Thank you.
>
> How are the patchsets different? As far as I know, all I did was apply
> the 3 patches that Neil added to my existing branch.
I'm not sure. I had a problem with your "multipath" branch before and
I recall what I did is went back and redownloaded your posted patches.
That was when I was testing performance. So if you haven't touched
that branch and just used it I think it's the same problem.
In the current testing branch I don't see several patches that Neil
has added (posted) to the mailing list. So I'm not sure what you mean
you added 3 of his patches on top of yours. At most I can say maybe
you added 2 of his (one that allows for v2 and v3 and another that
does state operations on a single connection. There are no patches for
sunrpc stats that were posted).
What I know is that if I revert your branch to
bf11fbdb20b385157b046ea7781f04d0c62554a3 before patches and apply
Neils patches. All is fine. I really don't want to debug a non-working
version when there is one that works.
>
> --
> Trond Myklebust
> Linux NFS client maintainer, Hammerspace
> trond.myklebust@hammerspace.com
>
>
next prev parent reply other threads:[~2019-07-11 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 19:06 multipath patches Olga Kornievskaia
2019-07-11 19:29 ` Trond Myklebust
2019-07-11 20:33 ` Olga Kornievskaia [this message]
2019-07-11 21:13 ` Trond Myklebust
2019-07-12 16:39 ` Olga Kornievskaia
2019-07-12 17:18 ` Trond Myklebust
2019-07-12 18:02 ` Olga Kornievskaia
2019-07-12 19:09 ` Trond Myklebust
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='CAN-5tyG0jdyn8C11v6b8=v3d1p=WoMAhXrAw8mWGEUn-TVXJ=g@mail.gmail.com' \
--to=aglo@umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.com \
--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;
as well as URLs for NNTP newsgroup(s).