Description of problem: I have lately been using ntfs-3g to mount my winxp partitions which I would also like to export across my network. However, I believe that this requires support for NFS to be compiled into the fuse module (according to README.NFS). I believe that this is not (yet) supported under the Fedora Extras version of Fuse. If it is supported, can you tell me what I need to do to make it work Any chance of adding such support in the (near) future? Specifically, I am in the current situation. If I mount my windows partitions using 'ntfs' then I have no trouble exporting them as nfs shares. However, if I mount the windows partitions using ntfs-3g (which uses FUSE) then they are no longer properly exported. Specifically, I get the error message: mount: 192.168.1.100:/mnt/winxp failed, reason given by server: Permission denied I tried adding fsid=NNN as recommended in the README.NFS but that didn't help, leading me to assume that maybe NFS support is not (yet) compiled into the fuse module.
Any chance of making this work????
> Any chance of making this work???? In any case there is a chance that it will work ) Possibly someone writes a HOWTO for this? I personally don't face such troubles 'cause don't share FUSE-filesystems via network.
Has this been fixed? Any interest in fixing it?
(In reply to comment #3) > Has this been fixed? I can't reproduce it personally (see reason above). Can you? > Any interest in fixing it? Sure, but I don't know how (1sr reason) and personally don't need such fix because I don't use NFS with FUSE (2nd reason). Maybe someone could fix?
Does this bug still exists with newer kernels?
Ping.
Assigning to kernel team.
This report makes it sound like we've forgotten to turn on some option. To the best of my knowledge, there is no option. If FUSE doesn't support NFS exporting, it's a shortcoming that needs to be addressed upstream.
Thats right, making an fielsystem exportable requires that it have a NON-null export_ops field in its superblock. FUSE currently has no export_ops defined.
I'm pretty sure the FUSE developer knows about this problem already.