From: Matthew Wilcox <willy@infradead.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: linux-xfs@vger.kernel.org, ritesh.list@gmail.com,
Pankaj Raghav <p.raghav@samsung.com>,
Daniel Gomez <da.gomez@samsung.com>
Subject: Re: Max theoretical XFS filesystem size in review
Date: Wed, 7 Feb 2024 22:39:00 +0000 [thread overview]
Message-ID: <ZcQGhFszPb5TaqA4@casper.infradead.org> (raw)
In-Reply-To: <ZcQDrXwyKxfTYpfL@bombadil.infradead.org>
On Wed, Feb 07, 2024 at 02:26:53PM -0800, Luis Chamberlain wrote:
> I'd like to review the max theoretical XFS filesystem size and
> if block size used may affect this. At first I thought that the limit which
> seems to be documented on a few pages online of 16 EiB might reflect the
> current limitations [0], however I suspect its an artifact of both
> BLKGETSIZE64 limitation. There might be others so I welcome your feedback
> on other things as well.
Linux is limited to 8EiB as loff_t is signed ... I don't want to introduce
lllseek() to expand beyond 8EiB; I have reason to believe that we'll
have 128-bit registers in relevant CPUs before we can buy reasonably
priced arrays of drives that will reach 8EiB (and want to turn those
into a single block device).
See my Zettalinux presentation at Plumbers 2022 in Dublin (and that
reminds me, I really should do something with zettalinux.org)
next prev parent reply other threads:[~2024-02-07 22:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 22:26 Max theoretical XFS filesystem size in review Luis Chamberlain
2024-02-07 22:39 ` Matthew Wilcox [this message]
2024-02-07 23:54 ` Dave Chinner
2024-03-15 0:12 ` Luis Chamberlain
2024-03-15 1:14 ` Dave Chinner
2024-03-15 2:48 ` Matthew Wilcox
2024-03-15 17:52 ` Luis Chamberlain
2024-03-18 0:00 ` Dave Chinner
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=ZcQGhFszPb5TaqA4@casper.infradead.org \
--to=willy@infradead.org \
--cc=da.gomez@samsung.com \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=p.raghav@samsung.com \
--cc=ritesh.list@gmail.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