From: Steve Cousins <steve.cousins@maine.edu>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: kyle <kylewong@southa.com>,
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 09:57:49 -0500 [thread overview]
Message-ID: <45B4D0ED.7030500@maine.edu> (raw)
In-Reply-To: <Pine.LNX.4.64.0701220717200.30260@p34.internal.lan>
Justin Piszcz wrote:
> 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!
Can you tell us when the "right" time is or maybe what the "wrong" time
is? Also, is this kernel specific? Does it (increasing
stripe_cache_size) work with RAID6 too?
Thanks,
Steve
--
______________________________________________________________________
Steve Cousins, Ocean Modeling Group Email: cousins@umit.maine.edu
Marine Sciences, 452 Aubert Hall http://rocky.umeoce.maine.edu
Univ. of Maine, Orono, ME 04469 Phone: (207) 581-4302
next prev parent reply other threads:[~2007-01-22 14:57 UTC|newest]
Thread overview: 18+ 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 14:56 ` Justin Piszcz
2007-01-22 15:18 ` kyle
2007-01-22 14:57 ` Steve Cousins [this message]
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=45B4D0ED.7030500@maine.edu \
--to=steve.cousins@maine.edu \
--cc=jpiszcz@lucidpixels.com \
--cc=kylewong@southa.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).