Can't access nfs shares mounted on NTFS partitions in F7

sideways · #1 3rd July 2007, 07:19 PM

I have a F7 machine which exports several nfs shares, the ext3 share is accessible with no problem using the same configuration as in FC6, but the NTFS exports are not accessible from a remote machine running FC6.

Here's how F7 mounts one of my NTFS partitions:

Code:

/dev/sdb1 on /mnt/win_c type fuseblk (ro,nosuid,nodev,noexec,noatime,allow_other,default_permissions,blksize=4096)

Here's the /etc/exports line for that partition

Code:

/mnt/win_c      10.0.0.2/255.255.255.0(ro,no_root_squash)

In FC6 this works fine, although the NTFS driver wasn't using fuse. I get no unusal messages in the logs, in fact /var/log/messages just indicates a succesful mount attempt from the remote client.

Has anyone else got a NTFS share in F7 accessible vis nfs? If so can you tell me how you are mounting the NTFS partition in F7 (eg post the output of mount)

linux_gentoo · #2 4th July 2007, 02:46 AM

Hello sideways, Did you install the fuse and ntfs-3g in the base system part of the F7 install. I did and it allows me to read/write NTFS access.

Perhaps you can go here: <<http://www.mjmwired.net/resources/mjm-fedora-f7.html#ntfs>> and this should get you going.

let us know if it works.

Seve · #3 5th July 2007, 03:42 AM

Hello sideways:

I tried to set up an old ntfs partition via nfs and was unsuccessful as well

F7
mtab:

Quote:

fuseblk rw,nosuid,nodev,noatime,allow_other,default_permis sions,blksize=4096 0 0

fstab:

Quote:

ntfs-3g rw,defaults,umask=000 0 0

Seve

sideways · #4 5th July 2007, 02:37 PM

I haven't had time to investigate this thoroughly, it is a strange problem which I have not encountered with previous fedora versions or other linux distros. I can mount the ntfs drives locally fine, it's just when trying to access them via nfs from another machine that I have the problem. No error messages are generated, ext3 partitions do not have the same problem and I have tried disabling selinux and firewall to no effect. setroubleshootd generates lots of messages relating to rpc.mountd but that doesn't seem to be the cause of the problem since disabling selinux doesn't help.

This is the one remaining issue with my F7 install.

Seve · #5 6th July 2007, 05:47 AM

Hello sideways:
If you happen to run across a solution please let me know.
I will do likewise.

Seve

szaka · #6 6th July 2007, 06:42 AM

http://ntfs-3g.org/support.html#nfs

Can I export NTFS via NFS?
Yes. But to do so, you need to read the FUSE README.NFS file and use the FUSE kernel module from the FUSE package because the mainstream kernels don't support NFS exporting of FUSE file systems.

sideways · #7 6th July 2007, 05:30 PM

Quote:

Originally Posted by szaka

http://ntfs-3g.org/support.html#nfs

Can I export NTFS via NFS?
Yes. But to do so, you need to read the FUSE README.NFS file and use the FUSE kernel module from the FUSE package because the mainstream kernels don't support NFS exporting of FUSE file systems.

I recompiled the kernel and added ntfs support as a module (I had to recompile the kernel anyway to add 8K stacks),

Code:

lsmod | grep fuse

fuse                   45653  10

local access to the ntfs partitions works fine it's just nfs remote access that is a problem.

I read README.NFS and tried adding fsid=0 to the export options but this doesn't work either. Should I be using some other number different to 0?

Like Seve I would be grateful if anyone who has this working could post the output of mount and their /etc/exports file. (Assuming you're using the fuse kernel module)

sideways · #8 6th July 2007, 09:49 PM

It's fixed now, using ntfs-3g

Thanks for the hint szaka, I removed the compiled fuse kernel module, downloaded the source for fuse-2.7, recompiled and used the --enable-kernel-module option with ./configure, then compiled the ntfs-3g package v1.616 (I can't install from the standard repos because my kernel is nonstandard). Then specified ntfs-3g as the filesystem in /etc/fstab rather than ntfs, rebooted and all seems fine now.

I don't understand the bit about adding fsid=NNN options to the exports, I didn't have to do this.

I probably haven't noticed that the kernel ntfs support didn't work with nfs in the past, hence my confusion, I should have just compiled and installed the separate ntfs or ntfs-3g kernel module as I have always done in the past.

Seve · #9 7th July 2007, 03:02 AM

Hello sideways:
Very good stuff

I would also like to say thanks to szaka as he is the man behind ntfs-3g

About NTFS-3G

Following your lead

I did some things a little bit different as I am using NFS4 and I did not have to build a custom kernel.

I downloaded the fuse.src.rpm and rebuilt it using the
--enable-kernel-module
versus the default
--disable-kernel-module
Then I replaced the current fuse, fuse-devel and fuse-libs packages with the new rpms.
The removal of the current fuse rpm's took ntfs-3g with it due to dependencies.
yum install ntfs-3g took care of it after the install of the new fuse rpms.
the /etc/fstab options for the ntfs partition
on the server looks like this
ntfs-3g rw,defaults,umask=000 0 0

Then
modprobe fuse

It works like a charm ......

Thanks again sideways ... great job !

Seve

Jongi · #10 9th August 2007, 03:24 PM

ah so it requires work to mount ntfs via nfs then. was wondering about this.

g8trGTO · #11 24th March 2008, 02:45 PM

Sorry to revive what seems like a dead thread, but I'm having a major issue trying to export NTFS via NFS. I've followed everything in this thread (as well as a number of other threads). However when I mount the share on the client, I simply get a blank, empty directory.

I've compiled both ntfs-3g and fuse from source with the --enable-kernel-module option in fuse. Modprobe shows that the fuse.ko module is installed.

Here are my steps. Please tell me where I'm going wrong. I've been mashing my head on this for a few days.

mount -t ntfs-3g -o ro,loop,offset=32256,utf8 /metadata/images/Backup.dd /nfs/disk

Code:

[root@headnode] mount
/dev/sda1 on / type ext3 (rw)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
/dev/loop2 on /nfs/disk type fuseblk (ro,noatime,allow_other,blksize=4096)
[root@headnode] cat /etc/exports
/nfs    10.1.1.0/255.255.255.0(ro,sync,fsid=0,no_root_squash)
[root@headnode] service nfs status
rpc.mountd is running
nfsd is running
rpc.rquotad is running
[root@headnode] ls /nfs/disk
... all of the files are displayed here ...
[root@headnode] ls /nfs/test
HaloCE.zip   restore.py

Both the firewall and SELinux are disabled. Mounting the share on a remote computer provides the following:

Code:

[root@client1] mount headnode:/nfs /nfs
[root@client1] ls /nfs
disk   test
[root@client1] ls /nfs/disk
[root@client1] ls /nfs/test
HaloCE.zip   restore.py
[root@client1]

An 'ls' here results nothing. The share mounts properly but nothing is being shown in the 'disk' directory. If anyone has any suggestions please let me know. I'm obviously doing something wrong but I can't figure out where it is. Thanks for any / all help or advice.

Jongi · #12 11th August 2008, 10:20 PM

Quote:

Originally Posted by Seve

I downloaded the fuse.src.rpm and rebuilt it using the
--enable-kernel-module

How do you do this?