The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@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, Oleg Drokin <green@namesys.com>
Subject: Re: [reiserfs-dev] Results of testing Reiserfs on large block devices.
Date: Fri, 05 Jul 2002 19:29:24 +0400	[thread overview]
Message-ID: <3D25BB54.7010005@namesys.com> (raw)
In-Reply-To: 15653.12329.565726.228100@wombat.chubb.wattle.id.au

Peter Chubb wrote:

>Hi folks,
>   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 reasoning assumes that the number of bitmaps is given by the
>formula (number_of_blocks + (8 * blocksize - 1))/(8 * blocksize) where
>blocksize is 4096 bytes.  Thus 
>	  number_of_blocks = 8 * 4096 * (16384 - 1) - 1  [64 bit]
>								
>	  number_of_blocks = 8 * 4096 * (32768 - 1) - 1  [32 bit]
>
>Hacking mm/slab.c to increase the memory limit allowed larger
>filesystems to be mounted, but I haven't tested these thoroughly yet.
>--
>Dr Peter Chubb				    peterc@gelato.unsw.edu.au
>You are lost in a maze of BitKeeper repositories, all almost the same.
>
>
>
>  
>
Thanks for figuring this out.  Oleg will fix it.

-- 
Hans




      parent reply	other threads:[~2002-07-05 15:36 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 ` [reiserfs-dev] " Oleg Drokin
2002-07-05 15:29 ` 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=3D25BB54.7010005@namesys.com \
    --to=reiser@namesys.com \
    --cc=gelato@gelato.unsw.edu.au \
    --cc=green@namesys.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox