From: Jookia <contact@jookia.org>
To: Sascha Hauer <sha@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] fs: nfs: Error if a port is unregistered
Date: Thu, 2 Feb 2023 20:33:16 +1100 [thread overview]
Message-ID: <Y9uDXGfxDzX5D9nz@novena-choice-citizen> (raw)
In-Reply-To: <20230202073948.GL13319@pengutronix.de>
On Thu, Feb 02, 2023 at 08:39:48AM +0100, Sascha Hauer wrote:
> When this happens do we see a meaningful error message on the barebox
> side? From a feeling I would say -ECONNREFUSED might be a better error
> code, but I don't know if that's suitable for UDP connections.
Currently the error looks like this:
mounting failed with -110
ERROR: nfs nfs0: probe failed: Connection timed out
mount: Invalid argument
probe-> nfs0
lookup mount port failed with -110
ERROR: nfs nfs0: probe failed: Connection timed out
Now it looks like:
lookup mount port failed with -2
ERROR: nfs nfs0: probe failed: No such file or directory
mount: Invalid argument
probe-> nfs0
Not sure how this could be improved.
> Sascha
John.
next prev parent reply other threads:[~2023-02-02 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 22:34 John Watts
2023-02-02 7:39 ` Sascha Hauer
2023-02-02 9:33 ` Jookia [this message]
2023-02-02 9:45 ` Ahmad Fatoum
2023-02-02 10:31 ` John Watts
2023-02-02 10:54 ` Ahmad Fatoum
2023-02-02 11:20 ` [PATCH v2] " John Watts
2023-02-03 8:00 ` Sascha Hauer
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=Y9uDXGfxDzX5D9nz@novena-choice-citizen \
--to=contact@jookia.org \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.de \
/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