Re: md strange sync?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> On Thu, May 27, 2010 at 5:31 AM, jose nuno neto <jose.neto@xxxxxxxxxxx>
> wrote:
>> Hi2all
>>
>> I have RedHat 5.5 ( kernel  2.6.18-194.el5 ) and 2hard disk with raid1
>> with md
>>
>> I have this setup on several machines, and recently notice this messages
>> in /var/log/messages
>>
>> Are this normal? Seems a re-sync but happened on several machines..
>>
>> May 23 04:22:01 <kern.info> dc2-x6250-a kernel: md: syncing RAID array
>> md0
>> May 23 04:22:01 <kern.info> dc2-x6250-a kernel: md: minimum _guaranteed_
>> reconstruction speed: 1000 KB/sec/disc.
>> May 23 04:22:01 <kern.info> dc2-x6250-a kernel: md: using maximum
>> available idle IO bandwidth (but not more than 200000 KB/sec) for
>> reconstruction.
>> May 23 04:22:01 <kern.info> dc2-x6250-a kernel: md: using 128k window,
>> over a total of 256896 blocks.
>> May 23 04:22:01 <kern.info> dc2-x6250-a kernel: md: delaying resync of
>> md1
>> until md0 has finished resync (they share one or more physical units)
>> May 23 04:22:04 <kern.info> dc2-x6250-a kernel: md: md0: sync done.
>> May 23 04:22:04 <kern.info> dc2-x6250-a kernel: md: syncing RAID array
>> md1
>> May 23 04:22:04 <kern.info> dc2-x6250-a kernel: md: minimum _guaranteed_
>> reconstruction speed: 1000 KB/sec/disc.
>> May 23 04:22:04 <kern.info> dc2-x6250-a kernel: md: using maximum
>> available idle IO bandwidth (but not more than 200000 KB/sec) for
>> reconstruction.
>> May 23 04:22:04 <kern.info> dc2-x6250-a kernel: md: using 128k window,
>> over a total of 8193024 blocks.
>> May 23 04:23:41 <kern.info> dc2-x6250-a kernel: md: md1: sync done.
>>
>>
>> thanks for any info
>>
>> regards
>> jose
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>
> You probably have an automated scrubbing setup in a cronscript.  This
> is a good thing as it prevents silent write-errors from going
> un-detected until some other drive fails and you suddenly lack
> sufficient good devices for that stripe to recover it.

I have this service running
/etc/init.d/mdmonitor
with this command
mdadm --monitor --scan -f --pid-file=/var/run/mdadm/mdadm.pid

that should be the one, right?

> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux