All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Prakash K. Cheemplavam" <prakashkc@gmx.de>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.10-rc1 and prev] System unuseable while writing to disk
Date: Thu, 11 Nov 2004 08:07:08 +0100	[thread overview]
Message-ID: <41930F9C.8010308@gmx.de> (raw)
In-Reply-To: <41927019.9050508@tmr.com>


[-- Attachment #1.1: Type: text/plain, Size: 3940 bytes --]

Bill Davidsen wrote:
> Prakash K. Cheemplavam wrote:
> 
>> Hi,
>>
>> I have a problem which doesn't seem to be connected to the i/o 
>> schedulers, because all I tested (cfq, deadline, noop) show the same:
>>
>> While writing (when the kernel actually commits to hd) my system gets 
>> very unresponsive esp when another app I want to use wants to write 
>> (read?) from hd, as well. This is *not* a UDMA problem (at least no 
>> apparent...)! More specific:
>>
>> I wrote this primitive code for writing sequentially:
> 
> 
> May I suggest running "vmstat 1" while this is happening? Looking at the 
> waitio time vs. transfer rates might reveal something. If it all looks 

Here you go. I hope you can see anything. (I attached the file as well...):


procs -----------memory---------- ---swap-- -----io---- --system-- 
----cpu----
  r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us 
sy id wa
  0  0      0 775044  14520 136460    0    0   935    86 1251   909 13 
5 57 25
  0  0      0 775036  14520 136460    0    0     0     0 1270   536  1 
0 99  0
  0  0      0 775036  14520 136460    0    0     0     0 1225   655  1 
1 98  0
  0  0      0 775036  14520 136460    0    0     0     0 1187   530  1 
0 99  0
  0  0      0 775036  14520 136460    0    0     0     0 1184   517  0 
0 100  0
  0  0      0 775036  14520 136460    0    0     0     0 1188   548  1 
1 98  0
  0  0      0 774876  14532 136460    0    0    12     0 1185   681  2 
1 94  3
  0  0      0 774876  14532 136460    0    0     0     0 1185   479  0 
0 100  0
  0  0      0 774876  14532 136460    0    0     0     0 1180   436  1 
0 99  0
  1  1      0 571740  14732 333736    0    0    32 42628 1325   633  3 
43 52  2
  2  2      0 217812  15072 676648    0    0     0 45184 1523  1771 14 
78  0  8
  1  2      0 220436  15072 676648    0    0     0 49664 1582  1365  9 
6  0 85
  0  2      0  85460  15984 808012    0    0   164 73984 1487  1143 18 
32  0 49
  0  1      0  85716  15984 808140    0    0     0 29056 1493  1381  4 
6  0 90
  0  1      0  86100  15984 808140    0    0     0 40320 1420  1367  3 
2  0 95
  0  1      0  86100  15984 808140    0    0     0 44416 1386   693  0 
2  0 98
  0  1      0  86100  15984 808140    0    0     0 50304 1518  1413  5 
6  0 89
  0  1      0  86164  15984 808140    0    0     0 28544 1452   827  1 
2  0 97
  0  1      0  86292  15984 808140    0    0     0 35840 1386   809  1 
2  0 97
  0  1      0  86356  15984 808140    0    0     0 37376 1450  1373  3 
3  0 94
procs -----------memory---------- ---swap-- -----io---- --system-- 
----cpu----
  r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us 
sy id wa
  1  1      0  86484  15984 808140    0    0     0 42880 1752  2494  7 
6  0 87
  0  1      0  86484  15984 808140    0    0     0 31872 1608  2098  7 
4  0 89
  0  1      0  86484  15984 808140    0    0     0 45952 1530   795  1 
2  0 97
  0  1      0  86484  15984 808140    0    0     0 44288 1515   814  0 
3  0 97
  0  1      0  90580  15984 808140    0    0     0 29052 1471  1365  5 
5  0 90
  1  0      0  90148  16108 809356    0    0   976  2088 1383  1319 22 
11  0 67
  0  0      0  90148  16108 809360    0    0     4    16 1444   833 10 
5 84  1
  0  0      0  90148  16108 809360    0    0     0     0 1256   473  0 
0 100  0
  0  0      0  90148  16108 809360    0    0     0     0 1379   611  3 
1 96  0
  0  0      0  90148  16108 809360    0    0     0     0 1526  2439 16 
5 79  0
  0  0      0  90148  16164 809360    0    0     0   120 1563  1824 16 
4 80  0


Beginning and end the system is idle and then I start writing down the 
file. During that time thunderbird gets unusable.

> I can't say that I see any such thing with ext[23], so it may be a 
> reiser issue and someone else will have to help. Did you look at the 
> logs to see that there are no useful warnings there?

Nothing in the logs, unfortunately.

Cheers,

Prakash

[-- Attachment #1.2: vmstat.txt --]
[-- Type: application/pgp-keys, Size: 2768 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-11-11  7:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 21:47 [2.6.10-rc1 and prev] System unuseable while writing to disk Prakash K. Cheemplavam
2004-11-10 19:46 ` Bill Davidsen
2004-11-11  7:07   ` Prakash K. Cheemplavam [this message]
2004-11-11  7:33     ` Nick Piggin
2004-11-11  7:43       ` Prakash K. Cheemplavam
2004-11-20 14:13       ` Prakash K. Cheemplavam

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=41930F9C.8010308@gmx.de \
    --to=prakashkc@gmx.de \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.