Date: Mon, 30 Mar 2020 13:37:14 +0100 From: Steve O'Hara-Smith <steve@sohara.org> To: freebsd-questions@freebsd.org Cc: "@lbutlr" <kremels@kreme.com> Subject: Re: NFS exports Message-ID: <20200330133714.99a56bc51c36f809507d7d24@sohara.org> In-Reply-To: <EED12931-1F45-453B-9E86-CD894F5BECE2@kreme.com> References: <4D1B1F02-773C-4390-8E11-C59A4CCE5105@kreme.com> <20200329142545.9a5c14d8a52019cef0a0669b@sohara.org> <EED12931-1F45-453B-9E86-CD894F5BECE2@kreme.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 30 Mar 2020 01:15:14 -0600 "@lbutlr" <kremels@kreme.com> wrote: > On 29 Mar 2020, at 07:25, Steve O'Hara-Smith <steve@sohara.org> wrote: > > On Sun, 29 Mar 2020 06:39:54 -0600 "@lbutlr" <kremels@kreme.com> wrote: > >> /mnt/backups -alldirs [IP address of remote machine] > >> > >> bad exports list line '/mnt/backups': symbolic link in export path or > >> statfs failed > >> > The extraneous ’s’ was the issue, but there was no /mnt/backups folder or > symlink. Error message is really misleading; “/mnt/backups does not > exist” would be much better. To be fair to the error message author one good reason for statfs to fail is a non-existent path, but we both overlooked that aspect of the message :( It would be nice if instead of a list of possible reasons, the actual detected reason was displayed. But you know - patches always welcome - nobody capable has yet thought it important/irritating enough to make the effort (even if the code change is trivial that's not insignificant) and get it merged. There may even be a really good reason not to do it that escapes me. -- Steve O'Hara-Smith <steve@sohara.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200330133714.99a56bc51c36f809507d7d24>