linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Janek Kozicki <janek_listy@wp.pl>
To: linux-raid@vger.kernel.org
Subject: mismatch_cnt of 128 and 1408.
Date: Mon, 24 Mar 2008 08:36:51 +0100	[thread overview]
Message-ID: <20080324083651.444cbab3@absurd> (raw)

Hello,

My backup box with raid5 recently suffered a series of power
failures. Now I'm doing some recovery hoping that power surges did
not damage HDDs.

I have here
- md0 a raid1 of 3*1GB=1GB (root partition) and
- md1 a raid5 of 3*500GB=1000GB (backup partition) and
- md2 a raid1 of 3*4GB=4GB (swap).

I did following things:

1. power on the server, and incidentally mount count for md1 enforced
   an fsck which found two errors.

2. /usr/share/mdadm/checkarray -a
   which does a resync of all raid partitions. It takes 5 hours for
   the 1TB backup partition.

3. afterwards the command: cat /sys/block/md?/md/mismatch_cnt gave answer:
   md0: 128
   md1: 0
   md2: 1408

4. touch /forcefsck ; shutdown -r now

5. then after reboot: /usr/share/mdadm/checkarray -a ; cat /sys/block/md?/md/mismatch_cnt
   md0: 128
   md1: 0
   md2: 1408

Now I am alarmed that something might be wrong with the root
partition. From other posts I remember that mismatch count for swap
partitions is allowed to be nonzero.

I checked smart health status of HDDs with smartctl -H and the drives
are healthy.


Is mismatch count = 128 an indication of bad HDD? How to discover
which one is bad?

-- 
Janek Kozicki                                                         |

             reply	other threads:[~2008-03-24  7:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24  7:36 Janek Kozicki [this message]
2008-03-24 20:23 ` mismatch_cnt of 128 and 1408 Oliver Martin
2008-03-25  3:33 ` Neil Brown
2008-03-25 12:43   ` Janek Kozicki
2008-03-26  2:07   ` Guy Watkins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080324083651.444cbab3@absurd \
    --to=janek_listy@wp.pl \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).