On Wednesday January 24, [EMAIL PROTECTED] wrote:
>
> Okay-- thanks for the explanation and I will await a future patch..
>
This would be that patch. It doesn't seem to break anything, but I
haven't reproduced he bug yet (I think I need to reduce the amount of
memory I have available) so I have
On Thu, 25 Jan 2007, Neil Brown wrote:
> On Wednesday January 24, [EMAIL PROTECTED] wrote:
> > Here you go Neil:
> >
> > p34:~# echo 512 > /sys/block/md3/md/stripe_cache_size
> > p34:~# echo 1024 > /sys/block/md3/md/stripe_cache_size
> > p34:~# echo 2048 > /sys/block/md3/md/stripe_cache_size
>
On Wednesday January 24, [EMAIL PROTECTED] wrote:
> Here you go Neil:
>
> p34:~# echo 512 > /sys/block/md3/md/stripe_cache_size
> p34:~# echo 1024 > /sys/block/md3/md/stripe_cache_size
> p34:~# echo 2048 > /sys/block/md3/md/stripe_cache_size
> p34:~# echo 4096 > /sys/block/md3/md/stripe_cache_size
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,
I can try and do this later this week possibly.
Justin.
On Tue, 23 Jan 2007, Neil Brown wrote:
> On Monday January 22, [EMAIL PROTECTED] wrote:
> > 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 fr
On Tuesday January 23, [EMAIL PROTECTED] wrote:
>
> This patch will almost certainly fix the problem, though I would like
> to completely understand it first
Of course, that patch didn't compile The "GFP_IO" should have been
"GFP_NOIO".
As below.
NeilBrown
--
Av
On Monday January 22, [EMAIL PROTECTED] wrote:
> 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 s
2007 5:18 AM
Subject: Re: change strip_cache_size freeze the whole raid
On Mon, 22 Jan 2007, kyle wrote:
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
> 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 y
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 lie
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
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
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 lie
On Mon, 22 Jan 2007, kyle wrote:
> >
> > On Mon, 22 Jan 2007, kyle wrote:
> >
> > > 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 tha
On Mon, 22 Jan 2007, kyle wrote:
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
On Mon, 22 Jan 2007, kyle wrote:
> 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 st
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
17 matches
Mail list logo
