From: Oleg Drokin <green@namesys.com>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: reiserfs-dev@namesys.com, gelato@gelato.unsw.edu.au,
linux-kernel@vger.kernel.org
Subject: Re: [reiserfs-dev] Results of testing Reiserfs on large block devices.
Date: Fri, 5 Jul 2002 09:46:47 +0400 [thread overview]
Message-ID: <20020705094647.A1464@namesys.com> (raw)
In-Reply-To: <15653.12329.565726.228100@wombat.chubb.wattle.id.au>
Hello!
On Fri, Jul 05, 2002 at 03:35:37PM +1000, Peter Chubb wrote:
> I couldn't get Reiserfs to work on large devices. I've tracked the
> problem down.
> When Reiserfs is mounted, it tries to allocate a chunk of memory for
> bitmaps using kmalloc. The largest chunk allocatable by kmalloc is
> 128k. This limits the size of a reiserfs to just under 2TB on a
> 64-bit platform (16384 bitmaps times 8bytes per pointer) or just under
> 4TB on a 32 bit platform (32768 bitmaps times 4bytes per pointer).
This is true for 4k blocksize.
> Hacking mm/slab.c to increase the memory limit allowed larger
> filesystems to be mounted, but I haven't tested these thoroughly yet.
Since kernel is yet to support block devices bigger than 2Tb, this is not an
issue yet.
Also Hans have not found a sponsor to fund this stuff which is also a problem.
Besides stuff you've just pointed out, there are also 32bit limit on
blocknumbers present in reiserfs v3 (which gives us 16Tb or something like that
limit for 4k blocksize)
Bye,
Oleg
next prev parent reply other threads:[~2002-07-05 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-05 5:35 Results of testing Reiserfs on large block devices Peter Chubb
2002-07-05 5:46 ` Oleg Drokin [this message]
2002-07-05 15:29 ` [reiserfs-dev] " Hans Reiser
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=20020705094647.A1464@namesys.com \
--to=green@namesys.com \
--cc=gelato@gelato.unsw.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
--cc=reiserfs-dev@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.