From: "bmoon" <bo@anthologysolutions.com>
To: Oleg Drokin <green@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Mount and file system size issue
Date: Thu, 7 Nov 2002 16:30:17 -0800 [thread overview]
Message-ID: <031301c286be$0384ac90$6a01a8c0@bmoon> (raw)
In-Reply-To: 20020607200220.A1657@namesys.com
Reisers,
I have three questions related with this 4 months old issue.
- Still reiser2 or reiser4 do not support "on demand" bitmap read?
- What is the supporting block size on reiser2, and reiser4?
- I am going to build one big volume(LVM) out of 8 IDE disks and make
reiserfs on it.
Where does the system write the meta data(super block, bitmap,..) into?
Will it copy the same meta data on each disk?
Thanks,
Bo
----- Original Message -----
From: "Oleg Drokin" <green@namesys.com>
Subject: Re: [reiserfs-list] Mount and file system size issue
> Hello!
>
> reiserfs reading all of the bitmaps immediately and stick bitmaps in
the RAM.
> So if reading all of the bitmaps on 120G volume, that means
> reading 960 4k sectors off the media (each 32M there is bitmap on
disk).
> That would eat at least 4 megabytes of RAM.
> Actually if you can do a profiling to see what reiserfs does during
mounting,
> that would be interesting.
> Also you have not answered what kind of media you are using.
>
> ext2/3 read bitmap blocks on demand on the other side.
>
>
next prev parent reply other threads:[~2002-11-08 0:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8287102CFE5C31418556A13A4E5BEE91E95A77@sphynx.git.compgen.com>
[not found] ` <3CFFB2CA.6020300@namesys.com>
2002-06-06 21:09 ` Mount and file system size issue bo
2002-06-07 7:21 ` Oleg Drokin
2002-06-07 15:49 ` bo
2002-06-07 16:02 ` Oleg Drokin
2002-06-07 16:38 ` bo
2002-06-07 19:26 ` Oleg Drokin
2002-06-08 19:42 ` bo
2002-06-09 19:07 ` Oleg Drokin
2002-06-10 17:47 ` bo
2002-06-10 19:20 ` Oleg Drokin
2002-06-12 15:33 ` Kuba Ober
2002-06-12 18:38 ` Oleg Drokin
2002-06-12 18:55 ` Kuba Ober
2002-06-13 2:33 ` bscott
2002-06-13 2:17 ` bo
2002-11-08 0:30 ` bmoon [this message]
2002-11-18 6:30 ` Oleg Drokin
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='031301c286be$0384ac90$6a01a8c0@bmoon' \
--to=bo@anthologysolutions.com \
--cc=green@namesys.com \
--cc=reiserfs-list@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.