* mismatch_cnt = 128 for root (/) md raid1 device
@ 2007-05-26 9:11 Justin Piszcz
2007-05-30 12:06 ` Justin Piszcz
0 siblings, 1 reply; 2+ messages in thread
From: Justin Piszcz @ 2007-05-26 9:11 UTC (permalink / raw)
To: linux-raid
Kernel 2.6.21.3
Fri May 25 20:00:02 EDT 2007: Executing RAID health check for /dev/md0...
Fri May 25 20:00:03 EDT 2007: Executing RAID health check for /dev/md1...
Fri May 25 20:00:04 EDT 2007: Executing RAID health check for /dev/md2...
Fri May 25 20:00:05 EDT 2007: Executing RAID health check for /dev/md3...
Sat May 26 04:40:09 EDT 2007: cat /sys/block/md0/md/mismatch_cnt
Sat May 26 04:40:09 EDT 2007: 0
Sat May 26 04:40:09 EDT 2007: cat /sys/block/md1/md/mismatch_cnt
Sat May 26 04:40:09 EDT 2007: 0
Sat May 26 04:40:09 EDT 2007: cat /sys/block/md2/md/mismatch_cnt
Sat May 26 04:40:09 EDT 2007: 128
Sat May 26 04:40:09 EDT 2007: cat /sys/block/md3/md/mismatch_cnt
Sat May 26 04:40:09 EDT 2007: 0
Sat May 26 04:40:09 EDT 2007: The meta-device /dev/md0 has no mismatched
sectors.
Sat May 26 04:40:10 EDT 2007: The meta-device /dev/md1 has no mismatched
sectors.
Sat May 26 04:40:11 EDT 2007: The meta-device /dev/md2 has 128 mismatched
sectors.
Sat May 26 04:40:11 EDT 2007: Executing repair on /dev/md2
Sat May 26 04:40:12 EDT 2007: The meta-device /dev/md3 has no mismatched
sectors.
Sat May 26 05:00:14 EDT 2007: cat /sys/block/md0/md/mismatch_cnt
Sat May 26 05:00:14 EDT 2007: 0
Sat May 26 05:00:14 EDT 2007: cat /sys/block/md1/md/mismatch_cnt
Sat May 26 05:00:14 EDT 2007: 0
Sat May 26 05:00:14 EDT 2007: cat /sys/block/md2/md/mismatch_cnt
Sat May 26 05:00:14 EDT 2007: 0
Sat May 26 05:00:14 EDT 2007: cat /sys/block/md3/md/mismatch_cnt
Sat May 26 05:00:14 EDT 2007: 0
I often see 128 or so for the root volume (/) for my RAID1. Any idea? I
know when you reboot/shutdown a system with md raid1 it does not mount
uncleanly (I believe?).
Just curious why it happens on the root volume and if its something I
should be worried about?
md0=swap
md1=boot
md2=root
md3=raid5_volume
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: mismatch_cnt = 128 for root (/) md raid1 device
2007-05-26 9:11 mismatch_cnt = 128 for root (/) md raid1 device Justin Piszcz
@ 2007-05-30 12:06 ` Justin Piszcz
0 siblings, 0 replies; 2+ messages in thread
From: Justin Piszcz @ 2007-05-30 12:06 UTC (permalink / raw)
To: linux-raid
Asking again..
On Sat, 26 May 2007, Justin Piszcz wrote:
> Kernel 2.6.21.3
>
> Fri May 25 20:00:02 EDT 2007: Executing RAID health check for /dev/md0...
> Fri May 25 20:00:03 EDT 2007: Executing RAID health check for /dev/md1...
> Fri May 25 20:00:04 EDT 2007: Executing RAID health check for /dev/md2...
> Fri May 25 20:00:05 EDT 2007: Executing RAID health check for /dev/md3...
> Sat May 26 04:40:09 EDT 2007: cat /sys/block/md0/md/mismatch_cnt
> Sat May 26 04:40:09 EDT 2007: 0
> Sat May 26 04:40:09 EDT 2007: cat /sys/block/md1/md/mismatch_cnt
> Sat May 26 04:40:09 EDT 2007: 0
> Sat May 26 04:40:09 EDT 2007: cat /sys/block/md2/md/mismatch_cnt
> Sat May 26 04:40:09 EDT 2007: 128
> Sat May 26 04:40:09 EDT 2007: cat /sys/block/md3/md/mismatch_cnt
> Sat May 26 04:40:09 EDT 2007: 0
> Sat May 26 04:40:09 EDT 2007: The meta-device /dev/md0 has no mismatched
> sectors.
> Sat May 26 04:40:10 EDT 2007: The meta-device /dev/md1 has no mismatched
> sectors.
> Sat May 26 04:40:11 EDT 2007: The meta-device /dev/md2 has 128 mismatched
> sectors.
> Sat May 26 04:40:11 EDT 2007: Executing repair on /dev/md2
> Sat May 26 04:40:12 EDT 2007: The meta-device /dev/md3 has no mismatched
> sectors.
> Sat May 26 05:00:14 EDT 2007: cat /sys/block/md0/md/mismatch_cnt
> Sat May 26 05:00:14 EDT 2007: 0
> Sat May 26 05:00:14 EDT 2007: cat /sys/block/md1/md/mismatch_cnt
> Sat May 26 05:00:14 EDT 2007: 0
> Sat May 26 05:00:14 EDT 2007: cat /sys/block/md2/md/mismatch_cnt
> Sat May 26 05:00:14 EDT 2007: 0
> Sat May 26 05:00:14 EDT 2007: cat /sys/block/md3/md/mismatch_cnt
> Sat May 26 05:00:14 EDT 2007: 0
>
> I often see 128 or so for the root volume (/) for my RAID1. Any idea? I
> know when you reboot/shutdown a system with md raid1 it does not mount
> uncleanly (I believe?).
>
> Just curious why it happens on the root volume and if its something I should
> be worried about?
>
> md0=swap
> md1=boot
> md2=root
> md3=raid5_volume
>
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-05-30 12:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-05-26 9:11 mismatch_cnt = 128 for root (/) md raid1 device Justin Piszcz
2007-05-30 12:06 ` Justin Piszcz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).