From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Steve Cousins <steve.cousins@maine.edu>
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 10:01:37 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0701221000330.1711@p34.internal.lan> (raw)
In-Reply-To: <45B4D0ED.7030500@maine.edu>
On Mon, 22 Jan 2007, Steve Cousins wrote:
>
>
> 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
>
>
>
The wrong time (for me anyway) is when/or around the time in which kernel
is auto-detecting arrays/udev starts, when I put it there I get OOPSES all
over the screen and it gets really nasty. Basically the best time appears
to be right after the system has started up but I/O hasn't started hitting
the array yet. Tricky, I know.
Justin.
next prev parent reply other threads:[~2007-01-22 15:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001801c73e14$c3177170$28df0f3d@kylecea1512a3f>
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
2007-01-22 15:01 ` Justin Piszcz [this message]
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
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=Pine.LNX.4.64.0701221000330.1711@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=kylewong@southa.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®