Re: NFSv4: mount -t nsf4 not the same as mount_newnfs?

2010-02-09 Thread O. Hartmann
On 02/08/10 22:37, Rick Macklem wrote: On Mon, 8 Feb 2010, O. Hartmann wrote: So I guess the above one is the more 'transparent' one with respect to the future, when NFSv4 gets mature and its way as matured into the kernel? Yea, I'd only use mount -t newnfs if for some reason you want

Re: NFSv4: mount -t nsf4 not the same as mount_newnfs?

2010-02-09 Thread Rick Macklem
On Tue, 9 Feb 2010, O. Hartmann wrote: Well, I guess I havn't uderstood everything of NFSv4. The 'concept' of the 'root' is new to me, maybe there are some deeper explanation of the purpose? Are there supposed to be more than one 'root' enries or only one? Only to specify different

Re: NFSv4: mount -t nsf4 not the same as mount_newnfs?

2010-02-08 Thread Rick Macklem
On Mon, 8 Feb 2010, O. Hartmann wrote: Mounting the filessystem via mount_newnfs host:/path /path Oh, and you should set: sysctl vfs.newnfs.locallocks_enable=0 in the server, since I haven't fixed the local locking yet. (This implies that apps/daemons running locally on the server

Re: NFSv4: mount -t nsf4 not the same as mount_newnfs?

2010-02-08 Thread Rick Macklem
On Mon, 8 Feb 2010, O. Hartmann wrote: Mounting the filessystem via mount_newnfs host:/path /path works fine, but not mount -t nfs4 host:/path /path. The mount command can be either: mount -t nfs -o nfsv4 host:/path /path or mount -t newnfs -o nfsv4 host:/path /path (The above was what

Re: NFSv4: mount -t nsf4 not the same as mount_newnfs?

2010-02-08 Thread O. Hartmann
On 02/08/10 15:08, Rick Macklem wrote: On Mon, 8 Feb 2010, O. Hartmann wrote: Mounting the filessystem via mount_newnfs host:/path /path Oh, and you should set: sysctl vfs.newnfs.locallocks_enable=0 in the server, since I haven't fixed the local locking yet. (This implies that

Re: NFSv4: mount -t nsf4 not the same as mount_newnfs?

2010-02-08 Thread O. Hartmann
On 02/08/10 15:01, Rick Macklem wrote: On Mon, 8 Feb 2010, O. Hartmann wrote: Mounting the filessystem via mount_newnfs host:/path /path works fine, but not mount -t nfs4 host:/path /path. The mount command can be either: mount -t nfs -o nfsv4 host:/path /path or mount -t newnfs -o

Re: NFSv4: mount -t nsf4 not the same as mount_newnfs?

2010-02-08 Thread Rick Macklem
On Mon, 8 Feb 2010, O. Hartmann wrote: Oh, and you should set: sysctl vfs.newnfs.locallocks_enable=0 in the server, since I haven't fixed the local locking yet. (This implies that apps/daemons running locally on the server won't see byte range locks performed by NFSv4 clients.) However,

Re: NFSv4: mount -t nsf4 not the same as mount_newnfs?

2010-02-08 Thread Rick Macklem
On Mon, 8 Feb 2010, O. Hartmann wrote: So I guess the above one is the more 'transparent' one with respect to the future, when NFSv4 gets mature and its way as matured into the kernel? Yea, I'd only use mount -t newnfs if for some reason you want to test/use the experimental client for

Re: NFSv4: mount -t nsf4 not the same as mount_newnfs?

2010-02-08 Thread Freddie Cash
On Mon, Feb 8, 2010 at 2:37 PM, Rick Macklem rmack...@uoguelph.ca wrote: ps: ZFS also has its own export stuff, but it is my understanding that putting a line in /etc/exports is sufficient. I've never used ZFS, so others will know more than I. My understanding (from having used NFS and