Date: Tue, 23 May 2017 22:07:23 +0000 From: Colin Percival <cperciva@tarsnap.com> To: Allan Jude <allanjude@freebsd.org>, Alexey Dokuchaev <danfe@FreeBSD.org>, Ed Maste <emaste@FreeBSD.org> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r318757 - head Message-ID: <0100015c3759afc2-0f5555cc-ea90-46d0-bebc-7566c190e860-000000@email.amazonses.com> In-Reply-To: <ba65ecaa-2999-e1df-e1bc-f251a1e709da@freebsd.org> References: <201705232025.v4NKPnrH001395@repo.freebsd.org> <20170523213306.GA74154@FreeBSD.org> <ba65ecaa-2999-e1df-e1bc-f251a1e709da@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/23/17 14:39, Allan Jude wrote: > On 2017-05-23 17:33, Alexey Dokuchaev wrote: >> On Tue, May 23, 2017 at 08:25:49PM +0000, Ed Maste wrote: >>> New Revision: 318757 >>> URL: https://svnweb.freebsd.org/changeset/base/318757 >>> >>> Log: >>> Add note to UPDATING for ino64 to follow the standard upgrade process >>> ... >>> +20170523: >>> + The "ino64" 64-bit inode project has been committed, which extends >>> + a number of types to 64 bits. >> >> For the dumb people among us, what is it all about? E.g., what's so cool >> about it? > > 64bit inodes allow you to have more than 4 billion files in one file > system, or NFS mount. It can avoid problems on NFS even if you have less than 2^32 files, since NFS uses 64-bit fileids and is not required to use the values 0, 1, 2, 3... for files. In Amazon EFS for example every fileid is > 2^32 and there's no guarantee that two files won't map to the same 32-bit inode # (pre-ino64, we simply reduced the fileid mod 2^32 to generate an inode #). -- 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?0100015c3759afc2-0f5555cc-ea90-46d0-bebc-7566c190e860-000000>