| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1166472455.5742.48.camel@lade.trondhjem.org> Date: Mon, 18 Dec 2006 15:07:35 -0500 From: Trond Myklebust <trond.myklebust@....uio.no> To: Justin Piszcz <jpiszcz@...idpixels.com> Cc: linux-kernel@...r.kernel.org Subject: Re: NFS Filesystem Size Limit? On Mon, 2006-12-18 at 14:21 -0500, Justin Piszcz wrote: > I have a question I could not quickly find on Google/mailing lists-- > > Say I have some sort of global filesystem or NFS which is 200TB. > > Is there a limit either: > > A) In the Linux kernel > or > B) In the NFS spec > > That would limit the client as to what it could see via NFS or global > filesystem? No. > Or could both 2.4 and 2.6 kernels 'see' the 200TB global filesystem over > NFS or global filesystem? 'df' may or may not report the filesystem size correctly (depends on whether you have VFS support for 64-bit filesystems enabled, and whether or not you are using NFSv3 or above), but you should be able to store 200TB worth or data on it irrespective of that. The one thing that may be limited is the size of individual files. The NFSv2 protocol limits file sizes to 2GB, whereas NFSv3 and v4 should allow you to read and write full 64-bit sized files. Note though, that on most 32-bit hardware, the Linux VM design limits you to 44-bit file sizes (due to the 32-bit page table + 4k page size). Cheers Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists