All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir V. Saveliev" <vs@namesys.com>
To: mingz@ele.uri.edu
Cc: reiserfs-list@namesys.com
Subject: Re: reiser fs slow on mksf and mount
Date: Fri, 26 Aug 2005 21:32:22 +0400	[thread overview]
Message-ID: <430F5226.50701@namesys.com> (raw)
In-Reply-To: <1125076558.5549.72.camel@localhost.localdomain>

Hello

Ming Zhang wrote:
> forget to mention that original mount is immediately after mkfs. so no
> files in fs at all.
> 
> now i create 1048576 4KB files
> 
> then umount and remount
> 
> [root@bakstor2u root]# time mount /dev/md0 t
> 
> real    1m10.971s
> user    0m0.001s
> sys     0m0.188s
> 
> almost same as first one.
> 
> this is from dmesg
> 
> ReiserFS: md0: found reiserfs format "3.6" with standard journal
> ReiserFS: md0: using ordered data mode
> ReiserFS: md0: journal params: device md0, size 8192, journal first
> block 18, max trans len 1024, max batch 900, max commit age 30, max
> trans age 30
> ReiserFS: md0: checking transaction log (md0)
> ReiserFS: md0: Using r5 hash to sort names
> 
> 
> so i could not understand why mount a fs with 0 files is same time with
> mount a fs with 1M files.
> 
> Thanks!
> 
> Ming
> 
> 
> 
> On Fri, 2005-08-26 at 13:08 -0400, Ming Zhang wrote:
>>i think 3.2TB partition is not that big these days right?
>>
>>i would think some people that hold millions of files will have much
>>larger partition than this.
>>
>>so you think this is a normal speed for such size partition?
>>

No. That was joke actually.
Speed of mkfs.reiserfs confuses me.
As you did answer about whether all disks were spinning - I suppose that they were.
Can you please run vmstat 1  or iostat 1 while mkreiserfs is running?

>>also iostat 1 -k shows that during mount, there are small size read
>>happen each second. so this is because read meta data and metadata is
>>not continuous on disk?
>>

Yes. On mount reiserfs reads all bitmap blocks to memory. Those blocks are spread over whole disk. There is workaround for this problem.

>>>>
>>>There is a patch to cure this problem.
>>>http://www.mail-archive.com/reiserfs-list@namesys.com/msg18442.html
>>>Please note that it is experimental one.
>>>
>>>>
>>>>
> 
> 
> 


  reply	other threads:[~2005-08-26 17:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-26 16:45 reiser fs slow on mksf and mount Ming Zhang
2005-08-26 17:04 ` Vladimir V. Saveliev
2005-08-26 17:08   ` Ming Zhang
2005-08-26 17:15     ` Ming Zhang
2005-08-26 17:32       ` Vladimir V. Saveliev [this message]
2005-08-26 18:07         ` Ming Zhang
2005-08-26 18:16         ` Ming Zhang
2005-08-27 19:29           ` Jeff Mahoney
2005-08-27 21:45             ` Christian Iversen
2005-08-27 21:55               ` David Masover
2005-08-29 19:44                 ` Hans Reiser
2005-08-27 22:54               ` Ming Zhang
2005-08-29 15:07               ` Jeff Mahoney
2005-08-27 22:53             ` Ming Zhang
2005-08-28  0:01               ` Jeff Mahoney
2005-08-28 15:40                 ` Ming Zhang
2005-08-28 18:44                   ` Jeff Mahoney
2005-08-29 12:39                     ` Ming Zhang
2005-08-29 14:26                       ` Jeff Mahoney
2005-08-29 14:41                         ` Ming Zhang
2005-08-29 14:51                           ` Jeff Mahoney
2005-08-29 15:20                             ` Ming Zhang
2005-08-29 15:28                               ` Jeff Mahoney
2005-08-29 15:37                                 ` Ming Zhang
2005-08-29 19:40             ` Hans Reiser
2005-08-29 19:44               ` Jeff Mahoney
2005-08-29 19:53                 ` Hans Reiser
2005-08-29 16:44   ` Ming Zhang

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=430F5226.50701@namesys.com \
    --to=vs@namesys.com \
    --cc=mingz@ele.uri.edu \
    --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.