Mr. James W. Laferriere wrote:
Hello Gabor ,
On Tue, 20 Jun 2006, Gabor Gombas wrote:
On Tue, Jun 20, 2006 at 03:08:59PM +0200, Niccolo Rigacci wrote:
Do you know if it is possible to switch the scheduler at runtime?
echo cfq > /sys/block//queue/scheduler
At least one can do a
On Tue, Jun 20, 2006 at 08:00:13AM -0700, Mr. James W. Laferriere wrote:
> At least one can do a ls of the /sys/block area & then do an
> automated
> echo cfq down the tree . Does anyone know of a method to set a
> default
> scheduler ?
RTFM: Documentation/kernel-
> At least one can do a ls of the /sys/block area & then do an
> automated
> echo cfq down the tree . Does anyone know of a method to set a
> default
> scheduler ?
My be I didn't understand the question...
You decide what schedulers are available at kernel compile
Hello Gabor ,
On Tue, 20 Jun 2006, Gabor Gombas wrote:
On Tue, Jun 20, 2006 at 03:08:59PM +0200, Niccolo Rigacci wrote:
Do you know if it is possible to switch the scheduler at runtime?
echo cfq > /sys/block//queue/scheduler
At least one can do a ls of the /sys/block area & t
On Tue, Jun 20, 2006 at 03:08:59PM +0200, Niccolo Rigacci wrote:
> Do you know if it is possible to switch the scheduler at runtime?
echo cfq > /sys/block//queue/scheduler
Gabor
--
-
MTA SZTAKI Computer and Automation Research I
On Mon, Jun 19, 2006 at 05:05:56PM +0200, Gabor Gombas wrote:
>
> IMHO a much better fix is to use the cfq I/O scheduler during the
> rebuild.
Yes, changing the default I/O to DEFAULT_CFQ solve the problem
very well, I get over 40 Mb/s resync speed with no lock-up at
all!
Thank you very much,
On Wed, Jun 14, 2006 at 10:46:09AM -0500, Bill Cizek wrote:
> I was able to work around this by lowering
> /proc/sys/dev/raid/speed_limit_max to a value
> below my disk thruput value (~ 50 MB/s) as follows:
IMHO a much better fix is to use the cfq I/O scheduler during the
rebuild. The default an
On Thursday 15 June 2006 12:13, you wrote:
> If this is causing a lockup, then there is something else wrong, just
> as any single process should not - by writing constantly to disks - be
> able to clog up the whole system.
>
> Maybe if you could get the result of
> alt-sysrq-P
I tried some kern
On Thursday June 15, [EMAIL PROTECTED] wrote:
> On Wed, Jun 14, 2006 at 10:46:09AM -0500, Bill Cizek wrote:
> > Niccolo Rigacci wrote:
> >
> > >When the sync is complete, the machine start to respond again
> > >perfectly.
> > >
> > I was able to work around this by lowering
> > /proc/sys/dev/rai
On Wed, Jun 14, 2006 at 10:46:09AM -0500, Bill Cizek wrote:
> Niccolo Rigacci wrote:
>
> >When the sync is complete, the machine start to respond again
> >perfectly.
> >
> I was able to work around this by lowering
> /proc/sys/dev/raid/speed_limit_max to a value
> below my disk thruput value (~
Niccolo Rigacci wrote:
Hi to all,
I have a new IBM xSeries 206m with two SATA drives, I installed a
Debian Testing (Etch) and configured a software RAID as shown:
Personalities : [raid1]
md1 : active raid1 sdb5[1] sda5[0]
1951744 blocks [2/2] [UU]
md2 : active raid1 sdb6[1] sda6[0]
11 matches
Mail list logo