From: Dave Chinner <david@fromorbit.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
Matthew Wilcox <willy@infradead.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: page->index limitation on 32bit system?
Date: Mon, 22 Feb 2021 11:19:30 +1100 [thread overview]
Message-ID: <20210222001930.GA4626@dread.disaster.area> (raw)
In-Reply-To: <df225e6c-b70d-fb2d-347c-55efa910cfdd@gmx.com>
On Sat, Feb 20, 2021 at 07:10:14AM +0800, Qu Wenruo wrote:
>
>
> On 2021/2/20 上午12:12, Theodore Ts'o wrote:
> > On Fri, Feb 19, 2021 at 08:37:30AM +0800, Qu Wenruo wrote:
> > > So it means the 32bit archs are already 2nd tier targets for at least
> > > upstream linux kernel?
> >
> > At least as far as btrfs is concerned, anyway....
>
> I'm afraid that would be the case.
>
> But I'm still interested in how other fses handle such problem.
Refuse to mount >16TB on 32 bit, 4kB page systems. And set the max
file offset for such systems to 16TB so sparse files can't be larger
than what the kernel supports. See xfs_sb_validate_fsb_count() call
and the file offset checks against MAX_LFS_FILESIZE in
xfs_fs_fill_super()...
FWIW, XFS has been doing this for roughly 20 years now - >16TB on 32
bit machines was an issue for XFS way back at the turn of the
century...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2021-02-22 0:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 8:54 page->index limitation on 32bit system? Qu Wenruo
2021-02-18 12:15 ` Matthew Wilcox
2021-02-18 12:42 ` Qu Wenruo
2021-02-18 13:39 ` Matthew Wilcox
2021-02-19 0:37 ` Qu Wenruo
2021-02-19 16:12 ` Theodore Ts'o
2021-02-19 23:10 ` Qu Wenruo
2021-02-20 0:23 ` Matthew Wilcox
2021-02-22 0:19 ` Dave Chinner [this message]
2021-02-20 2:20 ` Erik Jensen
2021-02-20 3:40 ` Matthew Wilcox
2021-02-20 23:02 ` Erik Jensen
2021-02-20 23:22 ` Matthew Wilcox
2021-02-21 0:01 ` Erik Jensen
2021-02-21 17:15 ` Matthew Wilcox
2021-02-18 21:27 ` Erik Jensen
2021-02-19 14:22 ` Matthew Wilcox
2021-02-19 17:51 ` Matthew Wilcox
2021-02-19 23:13 ` Qu Wenruo
2021-02-22 1:48 ` Dave Chinner
2021-03-01 1:49 ` GWB
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=20210222001930.GA4626@dread.disaster.area \
--to=david@fromorbit.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=tytso@mit.edu \
--cc=willy@infradead.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