From: James Simmons <jsimmons@infradead.org>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] lustre migration bug
Date: Mon, 26 Nov 2018 03:54:26 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.21.1811260347400.32255@casper.infradead.org> (raw)
Most of the major bugs outstanding are for migration functionality.
I did some tracing in the code (ll_migrate -> lmv_rename -> mdc_rename)
and found the failures is due to errors returned from after_reply() in
the ptlrpc layer. From that I see that the server is reporting that
the RPC packets are invalid. So far I don't see why exactly this is
the case. I will need to debug on the server side to figure it out.
reply other threads:[~2018-11-26 3:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LFD.2.21.1811260347400.32255@casper.infradead.org \
--to=jsimmons@infradead.org \
--cc=lustre-devel@lists.lustre.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.