Date: Thu, 14 Feb 2019 14:13:42 -0800 From: Colin Percival <cperciva@freebsd.org> To: Rafal Lukawiecki <raf@rafal.net>, freebsd-cloud@freebsd.org Subject: Re: Mounting NFS in FreeBSD 12.0 in AWS/EFS Message-ID: <252b4b78-fc20-df06-2487-a58355f79e04@freebsd.org> In-Reply-To: <B79B8571-1837-44BC-8FF3-412C8B6DCC80@rafal.net> References: <B79B8571-1837-44BC-8FF3-412C8B6DCC80@rafal.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/14/19 12:12 PM, Rafal Lukawiecki wrote: > In FreeBSD 11.1 I mount AWS EFS using: > > mount -t nfs -o > rw,nfsv4,oneopenown,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2 > > I understand that 12.0 had a few changes to NFS, including the long-awaited > support for 64-bit inodes. Is there a newer/better/more recommended way to > mount now? The same command should work just fine. > AWS suggest, for Linux, using nfsvers=4.1, and their mount looks > like this (I realise the slight difference in syntax): > > mount -t nfs4 > -o nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport The major difference here is that Linux doesn't need the 'oneopenown' option. But FreeBSD needs it in order to work around a limitation in how EFS tracks open files. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?252b4b78-fc20-df06-2487-a58355f79e04>