From: Matthew Wilcox <willy@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
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: Fri, 15 Mar 2024 02:48:27 +0000 [thread overview]
Message-ID: <ZfO2-wefNDEJGL5w@casper.infradead.org> (raw)
In-Reply-To: <ZfOg3dTO/R43FGiZ@dread.disaster.area>
On Fri, Mar 15, 2024 at 12:14:05PM +1100, Dave Chinner wrote:
> On Thu, Mar 14, 2024 at 05:12:22PM -0700, Luis Chamberlain wrote:
> > Joining two 8 EB files with device-mapper seems allowed:
> >
> > truncate -s 8EB /mnt-pmem/sparse-8eb.1; losetup /dev/loop1 /mnt-pmem/sparse-8eb.1
> > truncate -s 8EB /mnt-pmem/sparse-8eb.2; losetup /dev/loop2 /mnt-pmem/sparse-8eb.2
> >
> > cat /home/mcgrof/dm-join-multiple.sh
> > #!/bin/sh
> > # Join multiple devices with the same size in a linear form
> > # We assume the same size for simplicity
> > set -e
> > size=`blockdev --getsz $1`
> > FILE=$(mktemp)
> > for i in $(seq 1 $#) ; do
> > offset=$(( ($i -1) * $size))
> > echo "$offset $size linear $1 0" >> $FILE
> > shift
> > done
> > cat $FILE | dmsetup create joined
> > rm -f $FILE
> >
> > /home/mcgrof/dm-join-multiple.sh /dev/loop1 /dev/loop2
> >
> > And mkfs.xfs seems to go through on them, ie, its not rejected
>
> Ah, I think mkfs.xfs has a limit of 8EiB on image files, maybe not
> on block devices. What's the actual limit of block device size on
> Linux?
We can't seek past 2^63-1. That's the limit on lseek, llseek, lseek64
or whatever we're calling it these days. If we're missing a check
somewhere, that's a bug.
next prev parent reply other threads:[~2024-03-15 2:48 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
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 [this message]
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=ZfO2-wefNDEJGL5w@casper.infradead.org \
--to=willy@infradead.org \
--cc=da.gomez@samsung.com \
--cc=david@fromorbit.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