Date: Fri, 17 Jan 2025 17:14:30 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 280801] /bin/df -l reports remote (fuse) filesystems as local Message-ID: <bug-280801-227-F9ENcC28Of@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-280801-227@https.bugs.freebsd.org/bugzilla/> References: <bug-280801-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D280801 Alan Somers <asomers@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |Not Accepted --- Comment #7 from Alan Somers <asomers@FreeBSD.org> --- As discussed, there's no way for the kernel to know which fusefs file syste= ms are local and which remote. Nor is there any way for FreeBSD's VFS to know that certain mountpoints are local and certain remote, if they use the same file system. It's all-or-nothing. We could reclassify all fusefs file systems as remote to solve the OP's problem. However, I think the original motivation for the distinction was "local file systems are those I manage; remote ones are those that somebody else manages". By that standard, fusefs is a local file system, at least if it's something like fusefs-ext2. The OP's suggested workaround is a good one. I'm going to close this issue= as "Not accepted", given that it's not a bug and it's not a feature request we= can support. --=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-280801-227-F9ENcC28Of>