From: "kyle" <kylewong@southa.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>,
Steve Cousins <steve.cousins@maine.edu>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: change strip_cache_size freeze the whole raid
Date: Tue, 23 Jan 2007 22:22:51 +0800 [thread overview]
Message-ID: <009101c73ef9$fdb561d0$28df0f3d@kylecea1512a3f> (raw)
In-Reply-To: Pine.LNX.4.64.0701221000330.1711@p34.internal.lan
> I can try and do this later this week possibly.
> Justin.
>>
>> alt-sysrq-T or "echo t > /proc/sysrq-trigger" can be really helpful to
>> diagnose this sort of problem (providing the system isn't so badly
>> stuck that the kernel logs don't get stored).
>>
>> It is probably hitting a memory-allocation deadlock, though I cannot
>> see exactly where the deadlock would be. If you are able to reproduce
>> it and can get the kernel logs after 'alt-sysrq-T' I would really
>> appreciate it.
>> Justin,Maybe you can try freeze it once more and get the kernel logs
>> before try Neil's patch ...... :D~Kyle
WARNING: multiple messages have this Message-ID (diff)
From: "kyle" <kylewong@southa.com>
To: "Justin Piszcz" <jpiszcz@lucidpixels.com>,
"Steve Cousins" <steve.cousins@maine.edu>
Cc: <linux-raid@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: change strip_cache_size freeze the whole raid
Date: Tue, 23 Jan 2007 22:22:51 +0800 [thread overview]
Message-ID: <009101c73ef9$fdb561d0$28df0f3d@kylecea1512a3f> (raw)
In-Reply-To: Pine.LNX.4.64.0701221000330.1711@p34.internal.lan
> I can try and do this later this week possibly.
> Justin.
>>
>> alt-sysrq-T or "echo t > /proc/sysrq-trigger" can be really helpful to
>> diagnose this sort of problem (providing the system isn't so badly
>> stuck that the kernel logs don't get stored).
>>
>> It is probably hitting a memory-allocation deadlock, though I cannot
>> see exactly where the deadlock would be. If you are able to reproduce
>> it and can get the kernel logs after 'alt-sysrq-T' I would really
>> appreciate it.
>> Justin,Maybe you can try freeze it once more and get the kernel logs
>> before try Neil's patch ...... :D~Kyle
next prev parent reply other threads:[~2007-01-23 14:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 11:02 change strip_cache_size freeze the whole raid kyle
2007-01-22 12:18 ` Justin Piszcz
2007-01-22 13:09 ` kyle
2007-01-22 13:09 ` kyle
2007-01-22 14:56 ` Justin Piszcz
2007-01-22 15:18 ` kyle
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 [this message]
2007-01-23 14:22 ` kyle
2007-01-22 15:10 ` Justin Piszcz
2007-01-22 15:13 ` kyle
2007-01-22 15:13 ` kyle
2007-01-22 16:10 ` Liang Yang
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='009101c73ef9$fdb561d0$28df0f3d@kylecea1512a3f' \
--to=kylewong@southa.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=steve.cousins@maine.edu \
/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.