Report on issues with fusefs
Pavel Gorshkov
gorshkov.pavel at gmail.com
Sat Mar 23 21:52:41 UTC 2013
On Fri, Mar 22, 2013 at 10:16:09PM -0700, Kevin Oberman wrote:
> I've now been using fusefs regularly for a few months and I have found
> a few issues that i wanted to report.
>
> Most disturbing is corrupted NTFS systems. On several occasions I have
> found an NTFS system could not be written to with either FreeBSD or
> Windows. I had to user Windows disk check to repair the file system,
> but a few files were lost. this may be an issue with either fusefs or
> ntfs-3g. Not sure which, but it is likely tied to the next issue.
This patch, also referenced in ports/169165, might help solve at
least some of the issues:
http://www.mail-archive.com/freebsd-users-jp@jp.freebsd.org/msg04947.html
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/169165
-------------- next part --------------
--- fuse_vnops.c.old 2012-02-13 11:59:35.000000000 +0900
+++ fuse_vnops.c 2012-02-13 12:00:15.000000000 +0900
@@ -175,6 +175,11 @@
/* file ops */
static fo_close_t fuse_close_f;
+#if __FreeBSD_version > 900040
+static fo_chmod_t fuse_chmod_dummy;
+static fo_chown_t fuse_chown_dummy;
+#endif
+
/* vnode ops */
static vop_getattr_t fuse_getattr;
static vop_reclaim_t fuse_reclaim;
@@ -219,6 +224,10 @@
.fo_kqfilter = NULL,
.fo_stat = NULL,
.fo_close = fuse_close_f,
+#if __FreeBSD_version > 900040
+ .fo_chmod = fuse_chmod_dummy,
+ .fo_chown = fuse_chown_dummy,
+#endif
.fo_flags = DFLAG_PASSABLE | DFLAG_SEEKABLE
};
@@ -3659,3 +3668,17 @@
return (0);
}
#endif
+
+#if __FreeBSD_version > 900040
+static int
+fuse_chmod_dummy(struct file *fp, mode_t mode,
+ struct ucred *active_cred, struct thread *td) {
+ return (ENOSYS);
+}
+
+static int
+fuse_chown_dummy(struct file *fp, uid_t uid, gid_t gid,
+ struct ucred *active_cred, struct thread *td) {
+ return (ENOSYS);
+}
+#endif
More information about the freebsd-current
mailing list