Date: Thu, 19 Oct 2023 17:25:37 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 274600] /sbin/mount with invalid special device name gives confusing "Invalid fstype: Invalid argument" error Message-ID: <bug-274600-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D274600 Bug ID: 274600 Summary: /sbin/mount with invalid special device name gives confusing "Invalid fstype: Invalid argument" error Product: Base System Version: 15.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: martin@lispworks.com This error message is confusing because the fstype is not the problem: root@fb15:~ # uname -a FreeBSD fb15 15.0-CURRENT FreeBSD 15.0-CURRENT #0 main-n265728-8818f0f1124e: Thu Oct 5 03:15:28 UTC 2023=20=20=20=20 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 root@fb15:~ # mount /dev/foobar /mnt mount: /dev/foobar: Invalid fstype: Invalid argument root@fb15:~ #=20 In FreeBSD 12.4, it gave the correct error: mount: /dev/foobar: No such file or directory It looks like commit 6e8272f317b899438165108a72fa04a4995611bd might be to b= lame for this. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-274600-227>