From: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Fwd: component device mismatches found
Date: Sun, 19 Mar 2017 11:42:54 +0100 [thread overview]
Message-ID: <CAJH6TXhhYC0fenX3JZSwdaS+Rszdxkt8o4iLW6gK_dMsYe1JaA@mail.gmail.com> (raw)
In-Reply-To: <CAJH6TXhYYuh3v8FDDUisCpTZqVJ3WHEb_W0Ky=jkQHm1Y-fR4w@mail.gmail.com>
/cc linux-raid
---------- Forwarded message ----------
From: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
Date: 2017-03-19 11:42 GMT+01:00
Subject: Re: component device mismatches found
To: Wols Lists <antlists@youngman.org.uk>
2017-03-19 11:21 GMT+01:00 Wols Lists <antlists@youngman.org.uk>:
> mdadm --detail /dev/md/0
# mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Mon Jul 25 12:55:48 2016
Raid Level : raid1
Array Size : 488382841 (465.76 GiB 500.10 GB)
Used Dev Size : 488382841 (465.76 GiB 500.10 GB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistent
Update Time : Sun Mar 19 11:38:53 2017
State : clean, recovering
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Rebuild Status : 83% complete
Name : x:0 (local to host x)
UUID : b2a5ed53:42890b73:dc6de22a:1ac12524
Events : 29170
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
2 8 33 2 active sync /dev/sdc1
keep in mind that:
1) i've done a check this morning, after seeing the mismatch error in syslog
2) even this check has triggered a rebuild, probably due to the same mismatch.
3) SMART doesn't report any errors,
4) disks are "new", 5600 hours.
5) swap is still unused
prev parent reply other threads:[~2017-03-19 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 10:00 component device mismatches found Gandalf Corvotempesta
2017-03-19 10:21 ` Wols Lists
[not found] ` <CAJH6TXhYYuh3v8FDDUisCpTZqVJ3WHEb_W0Ky=jkQHm1Y-fR4w@mail.gmail.com>
2017-03-19 10:42 ` Gandalf Corvotempesta [this message]
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=CAJH6TXhhYC0fenX3JZSwdaS+Rszdxkt8o4iLW6gK_dMsYe1JaA@mail.gmail.com \
--to=gandalf.corvotempesta@gmail.com \
--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).