Subject: Re: stat64 for over 2TB file returned invalid st_blocks
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Takashi Sato <sho@bsd.tnes.nec.co.jp>,
       Dave Kleikamp <shaggy@austin.ibm.com>, linux-kernel@vger.kernel.org,
       linux-fsdevel@vger.kernel.org
In-Reply-To: <20051205081121.GU14509@schatzie.adilger.int>
References: <01e901c5f66e$d4551b70$4168010a@bsd.tnes.nec.co.jp>
	 <1133447539.8557.14.camel@kleikamp.austin.ibm.com>
	 <041701c5f742$d6b0a450$4168010a@bsd.tnes.nec.co.jp>
	 <20051202185805.GS14509@schatzie.adilger.int>
	 <02cd01c5f809$95a94620$4168010a@bsd.tnes.nec.co.jp>
	 <20051205081121.GU14509@schatzie.adilger.int>
Content-Type: text/plain
Date: Mon, 05 Dec 2005 08:34:17 -0500
Message-Id: <1133789657.8027.31.camel@lade.trondhjem.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 607
Lines: 16

On Mon, 2005-12-05 at 01:11 -0700, Andreas Dilger wrote:
> I don't know the exact specs of NFS v2 and v3, but I doubt they can have
> single files larger than 2TB.

The NFSv3 protocol supports file lengths up to and including 2^64,
however on 32-bit Linux clients, we're limited by the page cache's
inability to actually address more than 16TB.

Cheers,
  Trond

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/