Date: Sun, 28 Mar 2021 16:58:55 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 254625] FUSE filesystems do not report device name to devd Message-ID: <bug-254625-227-WXFrJ78enN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-254625-227@https.bugs.freebsd.org/bugzilla/> References: <bug-254625-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=3D254625 Alan Somers <asomers@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Not A Bug Status|New |Closed --- Comment #1 from Alan Somers <asomers@FreeBSD.org> --- This is not a bug in fusefs. The kernel has no idea which disk(s) a partic= ular fuse daemon may be using. It may be using 0, 1, or many real disks, but th= ose disks will all be opened by the daemon, not by fusefs itself. I think that you want may be one of the following two new features: 1) For bsdisks to monitor disk devices for open/close events instead of just mount/unmount, or 2) For ntfs-3g to report events to bsdisks directly I'm going to close this issue, because there's no bug in fusefs, and those = two features are both things that you should pursue upstream. But feel free to reopen it if there's something I'm not understanding, or if you have a bett= er idea. --=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-254625-227-WXFrJ78enN>