From: Eric Sandeen <sandeen@sandeen.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: xfs@oss.sgi.com
Subject: Re: Volume too big
Date: Sat, 19 Jan 2008 15:26:26 -0600 [thread overview]
Message-ID: <47926B02.709@sandeen.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0801192200390.4780@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Jan 19 2008 14:41, Eric Sandeen wrote:
>> It's possible that btrfs can cope with this somehow - but also quite
>> possible that it's just missing the right checks :)
>>
> I am not sure why Linux would be limited to 16 TB. If LBD is on,
> things are 64 bit, so I would expect to have at least access to
> 2 exabyte.
64-bit sector addressing, but there is a 32-bit index into the (4k)
pagecache.
2^32 * 4096 is 16T
So an address space has a 16T limit.
Even mkfs, if it needs to write past 16T (and I think mkfs.btrfs doesn't
need that...) will have trouble, if the device is > 16T - unless mkfs
uses direct IO.
-Eric
next prev parent reply other threads:[~2008-01-19 21:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 15:53 Volume too big Jan Engelhardt
2008-01-19 16:15 ` Eric Sandeen
2008-01-19 17:29 ` Justin Piszcz
2008-01-19 18:04 ` Jan Engelhardt
2008-01-19 17:53 ` Jan Engelhardt
2008-01-19 20:12 ` Eric Sandeen
2008-01-19 20:41 ` Eric Sandeen
2008-01-19 21:01 ` Jan Engelhardt
2008-01-19 21:26 ` Eric Sandeen [this message]
2008-01-20 22:03 ` Eric Sandeen
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=47926B02.709@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jengelh@computergmbh.de \
--cc=xfs@oss.sgi.com \
/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