mount ntfs, then nfs export it - empty folder shown on client

2011-08-29 Thread David Timms 
Hi, I have:
Server:
- ip=192.168.16.111
- ext4 partitions
- ntfs partition /dev/sda1

/etc/fstab mounts the ntfs partition at:
  /home/c-drive/

I can read/write that folder and it's directories from root and my user 
account (locally).

I setup nfs export of /home/ to 192.168.16.104


Client:
- ip=192.168.16.104
- mount -t nfs4 192.168.16.111:/ /home/dtnotebook/

- ls -l /home/dtnotebook
shows the folders including c-drive that are present on the server

- ls -l /home/dtnotebook/c-drive
shows no files nor folders present.

I googled my way around the earth and back, trying each suggestion, eg:
http://www.tuxera.com/community/ntfs-3g-faq/#nfs
http://forums.fedoraforum.org/showthread.php?t=159877

The info I have found (circa 2007) said you either need to:
1. recompile fuse source and create a new kernel module, but this seems 
to be working from fuse = 2.7.4, and to use:
2. use a kernel  2.6.14, which has the export of ntfs capability.

Anybody got this working, and/or could post the /etc/fstab and 
/etc/exports and the client command that are actually working ?
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Re: mount ntfs, then nfs export it - empty folder shown on client

2011-08-29 Thread Sam Sharpe 
On 29 August 2011 14:22, David Timms dti...@iinet.net.au wrote:

 I setup nfs export of /home/ to 192.168.16.104
 Client:
 - ip=192.168.16.104
 - mount -t nfs4 192.168.16.111:/ /home/dtnotebook/

 - ls -l /home/dtnotebook
 shows the folders including c-drive that are present on the server

 - ls -l /home/dtnotebook/c-drive
 shows no files nor folders present.

There are two relevant options for /etc/exports, but I will quote
directly from man(5) exports about crossmnt - you can investigate
nohide if you wish yourself.

crossmnt

This option is similar to nohide but it makes it possible for clients
to move from the filesystem marked with crossmnt to exported
filesystems mounted on it. Thus when a child filesystem B is mounted
on a parent A, setting crossmnt on A has the same effect as
setting nohide on B.

-- 
Sam
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines