From: Oleg Drokin <green@namesys.com>
To: bmoon <bo@anthologysolutions.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Mount and file system size issue
Date: Mon, 18 Nov 2002 09:30:54 +0300 [thread overview]
Message-ID: <20021118093054.A964@namesys.com> (raw)
In-Reply-To: <031301c286be$0384ac90$6a01a8c0@bmoon>
Hello!
On Thu, Nov 07, 2002 at 04:30:17PM -0800, bmoon wrote:
> I have three questions related with this 4 months old issue.
> - Still reiser2 or reiser4 do not support "on demand" bitmap read?
That's true for reiser3. reiser4 have on-demand bitmap reading,
but not unloading until umount as I remember.
> - What is the supporting block size on reiser2, and reiser4?
Right now due for simplicity reiser4 blocksize should be equal to
PAGE_CACHE_SIZE on underlying architecture.
reiser3 have 4096 bytes blocksize by default (this is the only supportted
blocksize for 2.4 kernel series). Other possible values are 1024, 2048, ...
and so on until you hit PAGE_CACHE_SIZE limit (Linux limit 4096 for x86,
8128 for Alpha, variable for ia64)
> - 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?
Superblock will be at the beginning of volume and will probably be mapped to
first disk. Bitmaps are spread over the disk (the ferquency of bitmaps
on disk depends on blocksize).
> Will it copy the same meta data on each disk?
No, unless you use RAID1 stuff, and even then this copying will be done
not by reiserfs itself.
Bye,
Oleg
prev parent reply other threads:[~2002-11-18 6: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
2002-11-18 6:30 ` Oleg Drokin [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=20021118093054.A964@namesys.com \
--to=green@namesys.com \
--cc=bo@anthologysolutions.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.