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: [email protected]
> 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
