On Thursday June 22, [EMAIL PROTECTED] wrote:
> >
> Thanks Neil for your quick reply. Would it be possible to elaborate a
> bit on the problem and the solution? I guess I won't be on 2.6.18 for
> some time...
>
When an array has been idle (no writes) for a short time (20 or 200
ms, depending on
Neil Brown wrote:
On Thursday June 22, [EMAIL PROTECTED] wrote:
Marc L. de Bruin wrote:
Situation: /dev/md0, type raid1, containing 2 active devices
(/dev/hda1 and /dev/hdc1) and 2 spare devices (/dev/hde1 and /dev/hdg1).
Those two spare 'partitions' are the only partitions on those
On Thursday June 22, [EMAIL PROTECTED] wrote:
> Marc L. de Bruin wrote:
>
> > Situation: /dev/md0, type raid1, containing 2 active devices
> > (/dev/hda1 and /dev/hdc1) and 2 spare devices (/dev/hde1 and /dev/hdg1).
> >
> > Those two spare 'partitions' are the only partitions on those disks
> >
Marc L. de Bruin wrote:
Situation: /dev/md0, type raid1, containing 2 active devices
(/dev/hda1 and /dev/hdc1) and 2 spare devices (/dev/hde1 and /dev/hdg1).
Those two spare 'partitions' are the only partitions on those disks
and therefore I'd like to spin down those disks using hdparm for
o
Mark Hahn wrote:
>> There's much easier/simpler way to set default scheduler. As
>
> personally, I don't see any point to worrying about the default,
> compile-time or boot time:
>
> for f in `find /sys/block/* -name scheduler`; do echo cfq > $f; done
I agree -- if you're talking about changing
> There's much easier/simpler way to set default scheduler. As
personally, I don't see any point to worrying about the default,
compile-time or boot time:
for f in `find /sys/block/* -name scheduler`; do echo cfq > $f; done
-
To unsubscribe from this list: send the line "unsubscribe linux-raid"
This patch makes needlessly global code static.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
drivers/md/md.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-2.6.17-mm1-full/drivers/md/md.c.old 2006-06-21 22:59:44.0
+0200
+++ linux-2.6.17-mm1-full/drivers
David Greaves wrote:
How do I interpret:
bitmap: 0/117 pages [0KB], 1024KB chunk
in the mdstat output
what does it mean when it's, eg: 23/117
This refers to the in-memory bitmap (basically a cache of what's in the
on-disk bitmap -- it allows bitmap operations to be more efficient).
If
Niccolo Rigacci wrote:
[]
> From the command line you can see which schedulers are supported
> and change it on the fly (remember to do it for each RAID disk):
>
> # cat /sys/block/hda/queue/scheduler
> noop [anticipatory] deadline cfq
> # echo cfq > /sys/block/hda/queue/scheduler
>
> Othe
OK :)
David
Niccolo Rigacci wrote:
> Thanks to the several guys in this list, I have solved my problem
> and elaborated this, can be a new FAQ entry?
>
>
>
> Q: Sometimes when a RAID volume is resyncing, the system seems to
> locks-up: every disk activity is blocked until resync is done.
>
> A:
Thanks to the several guys in this list, I have solved my problem
and elaborated this, can be a new FAQ entry?
Q: Sometimes when a RAID volume is resyncing, the system seems to
locks-up: every disk activity is blocked until resync is done.
A: This is not strictly related to Linux RAID, this i
11 matches
Mail list logo
