From: Jan Kara <jack@suse.cz>
To: Spelic <spelic@shiftmail.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: On the 16TiB max file size limit (not filesystem limit)
Date: Tue, 20 Aug 2013 19:35:37 +0200 [thread overview]
Message-ID: <20130820173537.GA5030@quack.suse.cz> (raw)
In-Reply-To: <521135ED.6010101@shiftmail.org>
On Sun 18-08-13 23:00:29, Spelic wrote:
> Dear ext4 developers
> are there any plans to overcome the 16TiB maximum file size limit for ext4?
>
> Now that resize works across 16TiB boundary, many people could be
> interested in using ext4 as a slower but safer alternative to a
> distributed filesystem for large storages. However 16TiB filesize
> limit might be a problem if one wants to do big virtualization or
> anyway somehow nesting storage systems one into the other. Is the
> limit hard to fix?
It would mean an incompatible on disk format change in the format of
extent. So it's doable but definitely not trivial.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2013-08-21 7:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-18 21:00 On the 16TiB max file size limit (not filesystem limit) Spelic
2013-08-20 17:35 ` Jan Kara [this message]
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=20130820173537.GA5030@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=spelic@shiftmail.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;
as well as URLs for NNTP newsgroup(s).