All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir V. Saveliev" <vs@namesys.com>
To: mohammad.rahman@webalive.biz
Cc: reiserfs-list@namesys.com
Subject: Re: reiser4 sending process to D state
Date: Tue, 16 Aug 2005 14:38:01 +0400	[thread overview]
Message-ID: <4301C209.7000302@namesys.com> (raw)
In-Reply-To: <43012902.1010600@webalive.biz>

Hello

Mohammad A. Rahman wrote:
> Hello,
> 
> I am having an issue with reiser4. I am wondering if it is a known issue 
> for reiser4 or I have missed something along the path.
> 
> #cat /etc/redhat-release
> Red Hat Enterprise Linux ES release 3 (Taroon Update 5)
> 
> Downloaded 2.6.12 vanila kernel, applied mm2 patch (2.6.12-mm2) and then 
> aapplied reiser4 patch downloaded from namesys for 2.6.12-mm2 
> (ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.12-mm2/reiser4-vfs-3.patch). 
> Kernel compiles and boots ok.
> 
> Compiled libaal-1.0.5 and reiser4progs-1.0.5 with ./configure, make and 
> make install.
> 
> Created reiser4 fs on my disk (/usr/local/sbin/mkfs.reiser4  /dev/sda5)
> 
> Mounted the partition (/dev/sda5               /test                   
> reiser4 defaults        1 2)
> 
> "dmesg | grep reiser" shows:  loading reiser4 bitmap......done (181 
> jiffies)
> 
> But when I try to write big amount of data on that partition the process 
> hangs and goes to uninterruptible sleep (D) state.
> 
> the PS output shows:
> 
> root      2375  2.7  0.0  3828  692 pts/1    D    23:21   0:15 cp -i -r 
> /usr .
> 
> I can easily simulate it with  bonnie++
> 
> bonnie++ -u user:user -d /test -s 4096m -m hudson -n 32:100000:16:256 -b -q
> 
I just tried that on 2.6.12-mm2 + ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.12-mm2/reiser4-vfs-3.patch.
And I am afraid I was not able to reproduce the problem:

Version  1.03       ------Sequential Output------ --Sequential Input- --Random-
                     -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
hudson           4G 17979  81 36327  21 18649  15 16293  70 40979  13  93.0  25
                     ------Sequential Create------ --------Random Create--------
                     -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files:max:min        /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
    32:100000:16/256    42   5   307   9   203  12    41   5    72   2    22   1
hudson,4G,17979,81,36327,21,18649,15,16293,70,40979,13,93.0,25,32:100000:16/256,42,5,307,9,203,12,41,5,72,2,22,1

can you please provide more information about your environment: amount of ram, SMP or UP, etc.


  reply	other threads:[~2005-08-16 10:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 23:45 reiser4 sending process to D state Mohammad A. Rahman
2005-08-16 10:38 ` Vladimir V. Saveliev [this message]
2005-08-18  0:26   ` Mohammad A. Rahman
2005-08-21  9:04     ` Vladimir V. Saveliev
2005-08-22  1:41       ` Michael James
2005-08-16 11:50 ` Hans Reiser
2005-08-16 12:08   ` Vladimir V. Saveliev
2005-08-16 18:24     ` Nate Diller
2005-08-16 18:30       ` Hans Reiser
2005-08-16 18:28     ` Hans Reiser
  -- strict thread matches above, loose matches on Subject: below --
2006-01-04 23:21 Mohammad A. Rahman

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=4301C209.7000302@namesys.com \
    --to=vs@namesys.com \
    --cc=mohammad.rahman@webalive.biz \
    --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.