linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robbert Eggermont <R.Eggermont@tudelft.nl>
To: linux-nfs@vger.kernel.org
Subject: RPC UDP message size limit
Date: Fri, 1 Jun 2018 14:07:03 +0200	[thread overview]
Message-ID: <726a7d92-bcb0-6120-252c-26d3a0951ddc@tudelft.nl> (raw)

Recently we started hitting the libtirpc RPC UDP message size limit 
(tirpc/rpc/rpc.h: #define UDPMSGSIZE 8800) for 'showmount -e' from a 
NetApp filer (with around 25kB worth of exports). Only 8800 bytes are 
read, resulting in an abort with a "rpc mount export: RPC: Can't decode 
result" error.

Since it seems filers are already using a higher limit, should this 
limit be increased (at least for receiving, which should be safe)?

-- 
Robbert Eggermont
Intelligent Systems Support & Data Steward | TU Delft
+31 15 27 83234 | Building 28, Floor 5, Room W660
Available Mon, Wed-Fri

             reply	other threads:[~2018-06-01 12:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01 12:07 Robbert Eggermont [this message]
2018-06-01 16:11 ` RPC UDP message size limit Chuck Lever
2018-06-04 15:26   ` Robbert Eggermont
2018-06-04 15:49     ` Chuck Lever

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=726a7d92-bcb0-6120-252c-26d3a0951ddc@tudelft.nl \
    --to=r.eggermont@tudelft.nl \
    --cc=linux-nfs@vger.kernel.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 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).