From: "Andris Berzins" <pkix@inbox.lv>
To: linux-raid@vger.kernel.org
Subject: failed raid re-create changed dev size
Date: Tue, 11 Dec 2012 01:37:19 +0200 [thread overview]
Message-ID: <1355182639.50c6722fe15b2@mail.inbox.lv> (raw)
Hello,
I have raid5 with 6 devices. One drive died, however, I hot-removed the wrong one, so raid failed.
I found on internet that this can be fixed if I re-create raid with the same configuration, but with dead drive set as 'missing'.
I saved --examinate data for all drives, and re run raid creation:
mdadm --verbose --create /dev/md1 --level=5 --raid-devices=6 /dev/sdb missing /dev/sdc /dev/sdg /dev/sdf /dev/sde
However, I can not mount md1 and looks like it contains random data. The order is correct. However, I noticed that new raid device size is different from old one.
Old working raid --examine:
/dev/sdc:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 39f653e1:515c53b4:a88a1588:0bf0fd07
Name : spire:1 (local to host spire)
Creation Time : Fri Jun 29 01:59:00 2012
Raid Level : raid5
Raid Devices : 6
Avail Dev Size : 5860531120 (2794.52 GiB 3000.59 GB)
Array Size : 14651325440 (13972.59 GiB 15002.96 GB)
Used Dev Size : 5860530176 (2794.52 GiB 3000.59 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 93e652d6:35c69c71:501601cd:7e640042
Update Time : Sun Dec 9 19:50:50 2012
Checksum : f30bd58d - correct
Events : 128287
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 2
Array State : ..A.AA ('A' == active, '.' == missing)
Re-created raid examine:
/dev/sdc:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 39f653e1:515c53b4:a88a1588:0bf0fd07
Name : spire:1 (local to host spire)
Creation Time : Mon Dec 10 21:04:01 2012
Raid Level : raid5
Raid Devices : 6
Avail Dev Size : 5860271024 (2794.40 GiB 3000.46 GB)
Array Size : 14650675200 (13971.97 GiB 15002.29 GB)
Used Dev Size : 5860270080 (2794.39 GiB 3000.46 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 4d0fe5bc:c05ec2c4:68805eab:bed7ef9c
Update Time : Mon Dec 10 21:04:39 2012
Checksum : 676939cb - correct
Events : 4
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 2
Array State : A.AAAA ('A' == active, '.' == missing)
So "Avail Dev Size" differs with re-created one being smaller for ~100MB.
What could be the reason why I can't mount re-created raid?
Idea: smartctl on one of drives shows 17 reallocated sectors:
5 Reallocated_Sector_Ct 0x0033 199 199 140 Pre-fail Always - 17
Could this be reason why re-created raid is smaller?
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2012-12-10 23:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 23:37 Andris Berzins [this message]
2012-12-11 8:15 ` failed raid re-create changed dev size Mikael Abrahamsson
2012-12-11 9:01 ` Andris Berzins
2012-12-11 9:27 ` Robin Hill
2012-12-11 14:35 ` Andris Berzins
2012-12-11 14:49 ` Robin Hill
2012-12-12 16:10 ` Andris Berzins
2012-12-13 9:30 ` Robin Hill
2012-12-13 16:13 ` Andris Berzins
2012-12-12 1:04 ` Brad Campbell
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=1355182639.50c6722fe15b2@mail.inbox.lv \
--to=pkix@inbox.lv \
--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).