From: "kyle" <kylewong@southa.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: change strip_cache_size freeze the whole raid
Date: Mon, 22 Jan 2007 23:18:35 +0800 [thread overview]
Message-ID: <00c201c73e38$95dcba70$28df0f3d@kylecea1512a3f> (raw)
In-Reply-To: Pine.LNX.4.64.0701220954540.1711@p34.internal.lan
>>
>> > Yes, I noticed this bug too, if you change it too many times or change
>> > it
>> > at the 'wrong' time, it hangs up when you echo numbr >
>> > /proc/stripe_cache_size.
>> >
>> > Basically don't run it more than once and don't run it at the 'wrong'
>> > time
>> > and it works. Not sure where the bug lies, but yeah I've seen that on
>> > 3
>> > different machines!
>> >
>> > Justin.
>> >
>> >
>>
>> I just change it once, then it freeze. It's hard to get the 'right time'
>>
>> Actually I tried it several times before. As I remember there was once it
>> freezed for around 1 or 2 minutes , then back to normal operation. This
>> is the
>> first time it completely freezed and I waited after around 10 minutes it
>> still
>> didn't wake up.
>>
>> Kyle
>>
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
> What kernel version are you using? It normally works the first time for
> me, I put it in my startup scripts, as one of the last items. However, if
> I change it a few times, it will hang and there is no way to reboot except
> via SYSRQ or pressing the reboot button on the machine.
>
> This seems to be true of 2.6.19.1 and 2.6.19.2, I did not try under
> 2.6.20-rc5 because I am tired of hanging my machine :)
>
> Justin.
>
It was 2.6.17.8. Now it's 2.6.7.13 but I won't touch it now! It's around
15km from me!
WARNING: multiple messages have this Message-ID (diff)
From: "kyle" <kylewong@southa.com>
To: "Justin Piszcz" <jpiszcz@lucidpixels.com>
Cc: <linux-raid@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: change strip_cache_size freeze the whole raid
Date: Mon, 22 Jan 2007 23:18:35 +0800 [thread overview]
Message-ID: <00c201c73e38$95dcba70$28df0f3d@kylecea1512a3f> (raw)
In-Reply-To: Pine.LNX.4.64.0701220954540.1711@p34.internal.lan
>>
>> > Yes, I noticed this bug too, if you change it too many times or change
>> > it
>> > at the 'wrong' time, it hangs up when you echo numbr >
>> > /proc/stripe_cache_size.
>> >
>> > Basically don't run it more than once and don't run it at the 'wrong'
>> > time
>> > and it works. Not sure where the bug lies, but yeah I've seen that on
>> > 3
>> > different machines!
>> >
>> > Justin.
>> >
>> >
>>
>> I just change it once, then it freeze. It's hard to get the 'right time'
>>
>> Actually I tried it several times before. As I remember there was once it
>> freezed for around 1 or 2 minutes , then back to normal operation. This
>> is the
>> first time it completely freezed and I waited after around 10 minutes it
>> still
>> didn't wake up.
>>
>> Kyle
>>
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
> What kernel version are you using? It normally works the first time for
> me, I put it in my startup scripts, as one of the last items. However, if
> I change it a few times, it will hang and there is no way to reboot except
> via SYSRQ or pressing the reboot button on the machine.
>
> This seems to be true of 2.6.19.1 and 2.6.19.2, I did not try under
> 2.6.20-rc5 because I am tired of hanging my machine :)
>
> Justin.
>
It was 2.6.17.8. Now it's 2.6.7.13 but I won't touch it now! It's around
15km from me!
next prev parent reply other threads:[~2007-01-22 15:18 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 [this message]
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-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='00c201c73e38$95dcba70$28df0f3d@kylecea1512a3f' \
--to=kylewong@southa.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.