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

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?
> 
> 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?
> 
> ming
> 
> 
> On Fri, 2005-08-26 at 21:04 +0400, Vladimir V. Saveliev wrote:
> > Hello
> > 
> > Ming Zhang wrote:
> > > Hi, folks
> > > 
> > > I am not sure if this is normal or not.
> > > 
> > > I try to create&use a reiserfs on a 8 disk raid0. Then I found that mkfs
> > > need ~90 sec and mount need ~70 seconds. 
> > > 
> > > Is there anything wrong on my side?
> > > 
> > 
> > Your device is too big.
> > 
> > > Thanks!
> > > 
> > > 
> > > Ming
> > > 
> > > 
> > > 
> > > Detailed info followed.
> > > ---------------------------------------------------------------------
> > > [root@bakstor2u root]# cat /proc/mdstat
> > > Personalities : [linear] [raid0] [raid1] [raid5] [multipath] [raid6]
> > > [raid10] [faulty]
> > > md0 : active raid0 sda[0] sdh[7] sdg[6] sdf[5] sde[4] sdd[3] sdc[2] sdb
> > > [1]
> > >       3125690368 blocks 64k chunks
> > > 
> > > unused devices: <none>
> > > 
> > > [root@bakstor2u root]# time mkfs.reiserfs /dev/md0 -ff
> > > mkfs.reiserfs 3.6.13 (2003 www.namesys.com)
> > > 
> > > <...>
> > > 
> > > Guessing about desired format.. Kernel 2.6.11.12 is running.
> > > Format 3.6 with standard journal
> > > Count of blocks on the device: 781422592
> > > Number of blocks consumed by mkreiserfs formatting process: 32059
> > > Blocksize: 4096
> > > Hash function used to sort names: "r5"
> > > Journal Size 8193 blocks (first block 18)
> > > Journal Max transaction length 1024
> > > inode generation number: 0
> > > UUID: 98d990f3-d54f-43e3-9fde-8c9c9a6d3481
> > > Initializing journal - 0%....20%....40%....60%....80%....100%
> > > Syncing..ok
> > > 
> > > Tell your friends to use a kernel based on 2.4.18 or later, and
> > > especially not a
> > > kernel based on 2.4.9, when you use reiserFS. Have fun.
> > > 
> > > ReiserFS is successfully created on /dev/md0.
> > > 
> > > real    1m28.783s
> > > user    0m0.151s
> > > sys     0m0.398s
> > > 
> > 
> > Hmm, mkfs.reiserfs had to write 32059 blocks. It is about 131mb. 1m28s is too much for that.
> > Could it be that some of disks used in that raid were not spinning when you started mkreiserfs?
> > 
> > > [root@bakstor2u root]# time mount /dev/md0  t
> > > 
> > > real    1m11.448s
> > > user    0m0.000s
> > > sys     0m0.225s
> > > 
> > 
> > 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:15 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 [this message]
2005-08-26 17:32       ` Vladimir V. Saveliev
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=1125076558.5549.72.camel@localhost.localdomain \
    --to=mingz@ele.uri.edu \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@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.