From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS Filesystem Size Limit?
Date: Mon, 18 Dec 2006 15:07:35 -0500 [thread overview]
Message-ID: <1166472455.5742.48.camel@lade.trondhjem.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0612181419010.2396@p34.internal.lan>
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
next prev parent reply other threads:[~2006-12-18 20:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 19:21 Justin Piszcz
2006-12-18 20:07 ` Trond Myklebust [this message]
2006-12-18 20:08 ` Justin Piszcz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1166472455.5742.48.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®