Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "kyle" <kylewong@southa.com>
To: linux-raid@vger.kernel.org
Subject: change strip_cache_size freeze the whole raid
Date: Mon, 22 Jan 2007 19:02:08 +0800	[thread overview]
Message-ID: <001801c73e14$c3177170$28df0f3d@kylecea1512a3f> (raw)

Hi,

Yesterday I tried to increase the value of strip_cache_size to see if I can 
get better performance or not. I increase the value from 2048 to something 
like 16384. After I did that, the raid5 freeze. Any proccess read / write to 
it stucked at D state. I tried to change it back to 2048, read 
strip_cache_active, cat /proc/mdstat, mdadm stop, etc. All didn't return 
back. I even cannot shutdown the machine. Finally I need to press the reset 
button in order to get back my control.

Kernel is 2.6.17.8 x86-64, running at AMD Athlon3000+, 2GB Ram, 8 x Seagate 
8200.10 250GB HDD, nvidia chipset.

cat /proc/mdstat (after reboot):
Personalities : [raid1] [raid5] [raid4]
md1 : active raid1 hdc2[1] hda2[0]
      6144768 blocks [2/2] [UU]

md2 : active raid5 sdf1[7] sde1[6] sdd1[5] sdc1[4] sdb1[3] sda1[2] hdc4[1] 
hda4[0]
      1664893440 blocks level 5, 512k chunk, algorithm 2 [8/8] [UUUUUUUU]

md0 : active raid1 hdc1[1] hda1[0]
      104320 blocks [2/2] [UU]

Kyle


             reply	other threads:[~2007-01-22 11:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-22 11:02 kyle [this message]
2007-01-22 12:18 ` change strip_cache_size freeze the whole raid Justin Piszcz
2007-01-22 13:09   ` kyle
2007-01-22 14:56     ` Justin Piszcz
2007-01-22 15:18       ` kyle
2007-01-22 14:57   ` Steve Cousins
2007-01-22 15:01     ` Justin Piszcz
2007-01-23 14:22       ` kyle
2007-01-22 15:10     ` Justin Piszcz
2007-01-22 15:13     ` kyle
2007-01-22 16:10   ` Liang Yang
2007-01-22 20:23 ` Neil Brown
2007-01-22 22:47   ` Neil Brown
2007-01-23 10:57   ` Justin Piszcz
2007-01-24 23:24   ` Justin Piszcz
2007-01-25  0:13     ` Neil Brown
2007-01-25  0:16       ` Justin Piszcz
2007-01-25  2:29         ` Neil Brown

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='001801c73e14$c3177170$28df0f3d@kylecea1512a3f' \
    --to=kylewong@southa.com \
    --cc=linux-raid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox