LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 08-05-2012, 12:34 AM   #1
qlands
Member
 
Registered: Sep 2010
Posts: 53

Rep: Reputation: 0
Unhappy Getting a lot of unexpected io


Hi,

I am experiencing a lot of unexpected io in my machine. I have a 64bits, Core I7, 8 GB system with Slackware 13.37.

If I open for example QTCreator and close it just after I open it, I can see the second hard disk (sdb) working a lot and QTCreator hangs for few secods. I ran iostats at that moment and I get the following:

Code:
device mgr/s mgw/s    r/s    w/s    kr/s    kw/s   size queue   wait svc_t  %b     <- Starts closing
sda        0     0    0.0    0.0     0.0     0.0    0.0   0.0    0.0   0.0   0 
sdb        0     0    0.0    0.0     0.0     0.0    0.0   0.2    0.0   0.0  16 
                             extended device statistics                       
device mgr/s mgw/s    r/s    w/s    kr/s    kw/s   size queue   wait svc_t  %b 
sda        0     0    0.0    0.0     0.0     0.0    0.0   0.0    0.0   0.0   0 
sdb        0     0    0.0    0.0     0.0     0.0    0.0   1.0    0.0   0.0 100 
                             extended device statistics                       
device mgr/s mgw/s    r/s    w/s    kr/s    kw/s   size queue   wait svc_t  %b 
sda        0     0    0.0    0.0     0.0     0.0    0.0   0.0    0.0   0.0   0 
sdb        0     0    0.0    0.0     0.0     0.0    0.0   1.0    0.0   0.0 100 
                             extended device statistics                       
device mgr/s mgw/s    r/s    w/s    kr/s    kw/s   size queue   wait svc_t  %b 
sda        0     0    0.0    0.0     0.0     0.0    0.0   0.0    0.0   0.0   0 
sdb        0     0    0.0    0.0     0.0     0.0    0.0   1.1    0.0   0.0 100 
                             extended device statistics                       
device mgr/s mgw/s    r/s    w/s    kr/s    kw/s   size queue   wait svc_t  %b 
sda        0     0    0.0    0.0     0.0     0.0    0.0   0.0    0.0   0.0   0 
sdb        0    21    0.0   15.4     0.0    61.7    4.0  22.1  561.5  58.8  91 
                             extended device statistics                       
device mgr/s mgw/s    r/s    w/s    kr/s    kw/s   size queue   wait svc_t  %b 
sda        0     0    0.0    0.0     0.0     0.0    0.0   0.0    0.0   0.0   0 
sdb        0     0    0.0   22.5     0.0   171.9    7.7  12.2 1251.2  43.5  98 
                             extended device statistics                       
device mgr/s mgw/s    r/s    w/s    kr/s    kw/s   size queue   wait svc_t  %b 
sda        0     0    0.0    0.0     0.0     0.0    0.0   0.0    0.0   0.0   0 
sdb        0    14    0.0   22.3     0.0    97.2    4.4  22.1  546.4  45.5 100 
                             extended device statistics                       
device mgr/s mgw/s    r/s    w/s    kr/s    kw/s   size queue   wait svc_t  %b 
sda        0     0    0.0    0.0     0.0     0.0    0.0   0.0    0.0   0.0   0 
sdb        0     0    0.0   23.1     0.0   148.7    6.4   5.1  675.6  43.5 100 
                             extended device statistics                       
device mgr/s mgw/s    r/s    w/s    kr/s    kw/s   size queue   wait svc_t  %b 
sda        0     0    0.0    0.0     0.0     0.0    0.0   0.0    0.0   0.0   0 
sdb        0     0    0.0   22.3     0.0    89.0    4.0   3.3  198.7  45.5 100 
                             extended device statistics                       
device mgr/s mgw/s    r/s    w/s    kr/s    kw/s   size queue   wait svc_t  %b 
sda        0     0    0.0    0.0     0.0     0.0    0.0   0.0    0.0   0.0   0 
sdb        0     0    0.0   17.5     0.0    70.0    4.0   2.1  118.9  42.7  75 
                             extended device statistics                       
device mgr/s mgw/s    r/s    w/s    kr/s    kw/s   size queue   wait svc_t  %b 
sda        0     0    0.0    0.0     0.0     0.0    0.0   0.0    0.0   0.0   0 
sdb        0     0    0.0    0.0     0.0     0.0    0.0   0.0    0.0   0.0   0   <- End closing
I can see the hard disk 100 busy just by closing qtcreator.

Using iodump at the same moment I get:
Code:
TASK                   PID      TOTAL       READ      WRITE      DIRTY DEVICES
journald              2296        293          0        293          0 sdb3
flush-8:16           32604         63          0         63          0 sdb3, sdb1
kjournald             2294         19          0         19          0 sdb1
qtcreator            21722         13          0         13          0 sdb3
Both utilities point to sdb3. I don't get any messages in syslog or in messages. The df information is the following:
Code:
Filesystem     Type    1K-blocks     Used Available Use% Mounted on
/dev/root      ext3    137452716 14290704 116179764  11% /
/dev/sdb1      ext3    173023324 50169008 114065160  31% /data
/dev/sdb2      ext3     19228308  4753268  13498288  27% /usr/local
/dev/sdb3      ext3     48062468  6301428  39319564  14% /home
tmpfs          tmpfs     4082892        0   4082892   0% /dev/shm
/dev/sda2      fuseblk 102297596 72373860  29923736  71% /win7
What can I do to check what is happening?

Many thanks,
Carlos
 
Old 08-05-2012, 04:59 AM   #2
Mark Pettit
Member
 
Registered: Dec 2008
Location: Cape Town, South Africa
Distribution: Slackware 14.1 64 Multi-Lib
Posts: 439

Rep: Reputation: 138Reputation: 138
Try 'iotop'. It will show you exact processes are writing to disk. I run it like this : iotop -o -d 5, which says only show processes doing actual i/o, and delay for 5 seconds to accumulate info. After that, once you see exactly what program is writing to disk (and you don't expect it to), you can use 'strace' to see exactly what is going on. You need to identify the process by it's pid - lets say it's pid 9999. The run 'strace -p 9999 -f'. This can generate a LOT of data if the process is very active, so consider redirecting to a file ( > /tmp/strace.txt). Finally, as it's really only disk-io you want to see, you can specify which system calls to trace, so, from the man page i see you can do this by appending '-e trace=open,close,read,write' to the strace command.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
A Few Scripts I Use A Lot dudeman41465 Programming 1 04-19-2010 12:39 PM
Noobie in need of a lot of help donang72 Linux - Networking 11 06-17-2007 05:57 PM
a lot of problems kryckan Linux - Hardware 4 10-04-2003 08:37 AM
Thanks a Lot! XPediTioN Slackware 0 07-11-2003 05:51 PM
There's a lot of Stephanies about... stephstellar General 3 02-03-2003 08:11 AM


All times are GMT -5. The time now is 02:34 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration