Date: Fri, 23 Feb 2024 16:41:44 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 277264] mount(8)ing incorrect device gives confusing ENOENT Message-ID: <bug-277264-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D277264 Bug ID: 277264 Summary: mount(8)ing incorrect device gives confusing ENOENT Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: lexi.freebsd@le-fay.org # mdconfig -l md0 # gpart show md0 =3D> 63 10485697 md0 MBR (5.0G) 63 1985 - free - (993K) 2048 102400 1 fat32lba [active] (50M) 104448 10381312 2 freebsd (5.0G) # ls -l /dev/md0s2 crw-r----- 1 root operator 0x211 Feb 23 16:33 /dev/md0s2 # mount -t ufs -rw /dev/md0s2 /mnt mount: /dev/md0s2: No such file or directory this was my error, because the correct device is /dev/md0s2a, not /dev/md0s= 2.=20 however, ENOENT seems like the wrong error here, because the device listed = in the error clearly does exist, it just doesn't contain a UFS filesystem.=20= =20 using 15.0-CURRENT 58df49801d9d58e61cc2adc8fd1e6848b64d2453 on amd64. --=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-277264-227>