All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Mark Knibbs <markk@clara.co.uk>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Possible ext2 bug with large sparse files?
Date: Tue, 5 Jun 2007 09:56:06 -0400	[thread overview]
Message-ID: <20070605135606.GE12755@thunk.org> (raw)
In-Reply-To: <E1HvY6M-000Ai0-Ff@oceanus.uk.clara.net>

On Tue, Jun 05, 2007 at 01:25:29PM +0100, Mark Knibbs wrote:
> For whatever reason, it seems the maximum file size for that
> partition is 17,247,252,480 bytes. In itself that behaviour isn't 
> necessarily a bug; but if you have any clue how the ext2 maximum file size 
> is related (or not) to the amount of free space or the volume size, please 
> let me know!

You're using a filesystem with a 1k blocksize, and that's the cause of
the limit.  The maximum number of 1k blocks that can be addressed
using the direct/indirect scheme is:

	12 + 256 + 256*256 + 256*256*256 = 16843020 blocks

or
	16843020 blocks * 1024 bytes/block =  17,247,252,480 bytes

Unless you are using a really tiny filesystem, you really don't want
to be using 1k block sizes; in addition to imposing this 16GB file
size limit, it also makes the filesystem much more inefficient for
large files.

Regards,

						- Ted

  reply	other threads:[~2007-06-05 13:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 12:25 Possible ext2 bug with large sparse files? Mark Knibbs
2007-06-05 13:56 ` Theodore Tso [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-06-06 13:18 Mark Knibbs
2007-06-07 17:51 ` Andreas Dilger
2007-06-07 21:40   ` Mark Knibbs

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=20070605135606.GE12755@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=markk@clara.co.uk \
    /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.