From: Hans Reiser <reiser@namesys.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Reiserfs mail-list <Reiserfs-List@Namesys.COM>,
Vladimir Saveliev <vs@namesys.com>
Subject: Re: ReiserFS Maximum file size (in practice)
Date: Tue, 18 May 2004 22:39:29 -0700 [thread overview]
Message-ID: <40AAF311.3020900@namesys.com> (raw)
In-Reply-To: <40AA74CA.5040306@suse.com>
Jeff Mahoney wrote:
>
> Hey all -
>
> The ReiserFS FAQ that we quote and point people to when they ask
> questions about limits in ReiserFS states that the maxmimum file size
> for a reiserfs v3 filesystem is 2^60-1. However, the actual limits, in
> practice, are far less.
>
> I tried to create a 3 TB sparse file, and ended up getting told it was
> too large. 2 TB was too large also, just under 2 TB was ok.
>
> This is a result of super->s_maxbytes = (512LL << 32) -
> s->s_blocksize;, in fs/reiserfs/super.c, which is set so that i_blocks
> isn't overflowed.
if vs approves it, I do.
>
> Other filesystems that have the ability to cross the 2 TB limit on
> file sizes simply ignore the limit and allow i_blocks to wrap. There's
> really no reason we can't do the same.
>
> The patch is attached.
>
> -Jeff
>
>------------------------------------------------------------------------
>
>--- linux-2.6.5/fs/reiserfs/super.c 2004-05-14 15:32:49.000000000 -0400
>+++ linux-2.6.5.fix/fs/reiserfs/super.c 2004-05-18 12:07:25.000000000 -0400
>@@ -1204,7 +1204,7 @@
> /* new format is limited by the 32 bit wide i_blocks field, want to
> ** be one full block below that.
> */
>- s->s_maxbytes = (512LL << 32) - s->s_blocksize ;
>+ s->s_maxbytes = MAX_LFS_FILESIZE;
> return 0;
> }
>
>
>
prev parent reply other threads:[~2004-05-19 5:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 20:40 ReiserFS Maximum file size (in practice) Jeff Mahoney
2004-05-19 0:45 ` Chris Mason
2004-05-19 8:33 ` Alex Zarochentsev
2004-05-19 12:13 ` Jeffrey Mahoney
2004-05-19 12:57 ` Chris Mason
2004-05-19 20:04 ` Jeff Mahoney
2004-05-19 5:39 ` Hans Reiser [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=40AAF311.3020900@namesys.com \
--to=reiser@namesys.com \
--cc=Reiserfs-List@Namesys.COM \
--cc=jeffm@suse.com \
--cc=vs@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.