RedShift <redshift@xxxxxxxxxx> wrote: > What exactly is the mismatch_cnt value? If it's not too much, it is most likely coming from your swap partition. 128. md0 is /boot only; swap is on md1 which didn't have a problem Devin -- A zygote is a gamete's way of producing more gametes. This may be the purpose of the universe. - Robert Heinlein _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
Re: mismatch_cnt after 5.3 -> 5.4 upgrade
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: CentOS mailing list <centos@xxxxxxxxxx>
- Subject: Re: mismatch_cnt after 5.3 -> 5.4 upgrade
- From: Devin Reade <gdr@xxxxxxx>
- Date: Sun, 25 Oct 2009 16:27:43 -0600
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <4AE49D86.2090400@xxxxxxxxxx>
- References: <AA2907DD311DF39C2520DC2A@xxxxxxxxxxxxxx> <4AE49D86.2090400@xxxxxxxxxx>
- References:
- mismatch_cnt after 5.3 -> 5.4 upgrade
- From: Devin Reade
- Re: mismatch_cnt after 5.3 -> 5.4 upgrade
- From: RedShift
- mismatch_cnt after 5.3 -> 5.4 upgrade
- Prev by Date: Re: Testing remote machine status in a script ?
- Next by Date: Re: mismatch_cnt after 5.3 -> 5.4 upgrade
- Previous by thread: Re: mismatch_cnt after 5.3 -> 5.4 upgrade
- Next by thread: Re: mismatch_cnt after 5.3 -> 5.4 upgrade
- Index(es):
 |