All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Anders Widman <andewid@tnonline.net>
Cc: reiserfs-list@namesys.com
Subject: Re: reiserfsprogs 3.6.5-pre2 release.
Date: Wed, 26 Feb 2003 15:42:30 +0300	[thread overview]
Message-ID: <20030226154230.A19240@namesys.com> (raw)
In-Reply-To: <865715375.20030226133422@tnonline.net>

Hello!

On Wed, Feb 26, 2003 at 01:34:22PM +0100, Anders Widman wrote:
> >> Would it be possible to lower the time it takes to mount a filesystem?
> >> Currently it takes about 48s to mount my fs:
> > Unfortunatelly there is no easy way.
> > Seems that most of the time is spent reading bitmaps (one bitmap after each 128M of data),
> > and reiserfs reads in all the bitmaps at once during mount.
> I  only  posted  this  because it is discussed how to lower the bootup
> time. The fsck might take a few seconds when optimised, but the actual
> mount of the FS takes much longer.

But this is not good reason to make it even longer, what do you think?
(and blockdev cache is flushed on last device close, so mount won't get
these bitmap blocks from cache).

> How  big  is  each  block  of bitmaps that is being read during mount?

it's of blocksize size (4k for now).

> Would  it  be  possible  to make the reads more efficient? I mean, now

You still need to seek to every of them.
(Other possibility is to read bitmap blocks on 1st access, but this is not very
easy task, I'd say).

> there  would  be 6400 reads on a 800GB FS. From the sound of the disks
> it does not seem as they work at 100% during mount?

Hm. Disk cannot do anything while it is seeking. Also since the seeks are
in one direction, you won't hear any unusual noises, I believe.

Bye,
    Oleg

  reply	other threads:[~2003-02-26 12:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25 13:50 reiserfsprogs 3.6.5-pre2 release Vitaly Fertman
2003-02-25 14:12 ` Vitaly Fertman
2003-02-26  0:54   ` Philippe Gramoullé
2003-02-26  7:29     ` Oleg Drokin
2003-02-26  8:23       ` Philippe Gramoullé
2003-02-26 11:27       ` Hans Reiser
2003-02-26 12:14         ` Anders Widman
2003-02-26 12:24           ` Oleg Drokin
2003-02-26 12:34             ` Anders Widman
2003-02-26 12:42               ` Oleg Drokin [this message]
2003-03-05  0:50 ` Zygo Blaxell
2003-03-05 17:48   ` Dieter Nützel
2003-03-05 18:10     ` Vitaly Fertman
2003-03-20 13:31 ` reiserfsprogs 3.6.5 release Vitaly Fertman
2003-03-20 15:45   ` Philippe Gramoullé
  -- strict thread matches above, loose matches on Subject: below --
2003-02-25 16:25 reiserfsprogs 3.6.5-pre2 release berthiaume_wayne
2003-02-25 16:41 ` Vitaly Fertman
2003-02-26 15:12 berthiaume_wayne
2003-02-26 16:14 ` Vitaly Fertman
2003-02-26 18:59   ` Hans Reiser
2003-02-26 19:21   ` Andreas Dilger
2003-02-26 23:40     ` Philippe Gramoullé
2003-02-27  6:11     ` Oleg Drokin
2003-02-26 23:49   ` Anders Widman
2003-02-27  6:13     ` 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=20030226154230.A19240@namesys.com \
    --to=green@namesys.com \
    --cc=andewid@tnonline.net \
    --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.