From: Konstantin Svist <fry.kun@gmail.com>
To: linux-raid@vger.kernel.org
Subject: messed up changing chunk size
Date: Sun, 18 Jul 2010 17:32:25 -0700 [thread overview]
Message-ID: <4C439D19.4070906@gmail.com> (raw)
I've been playing around with RAID config and may have finally messed
it up.
Initially, I created the array with 3 300G drives:
# mdadm --create --verbose /dev/md0 --level=5 --raid-devices=3 /dev/sda4
/dev/sdb1 /dev/sdc1
# mkfs.ext4 -v -m 0.01 -E stride=16,stripe-width=32 /dev/md0
It's been working nicely so far, and I decided to add a 4th 300G drive:
# mdadm --grow --raid-devices=4 --backup-file=/root/grow_md0.bak /dev/md0
That finished overnight, while I looked around and found that chunk size
of 512 should work better. I unmounted the FS and ran
# mdadm --grow -c 512 --backup-file=/root/grow_md0_rechunk.bak /dev/md0
mdadm: component size 293033536K is not a multiple of chunksize 512K
so I sized it down a bit:
# mdadm --grow -z 293033472 --backup-file=/root/grow_md0_size.bak /dev/md0
and then back to resizing chunks:
mdadm --grow -c 512 --backup-file=/root/grow_md0_rechunk.bak /dev/md0
It's running right now:
# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 sdd1[3] sda4[0] sdc1[2] sdb1[1]
293033472 blocks super 0.91 level 5, 64k chunk, algorithm 2 [4/4]
[UUUU]
[====>................] reshape = 22.7% (66540032/293033472)
finish=947.3min speed=3984K/sec
But just now I tried to mount the filesystem and it's failing:
EXT4-fs (md0): bad geometry: block count 146516768 exceeds size of
device (73258368 blocks)
Here's the question, then: am I royally screwed or is my data still
there? How do I recover?
Yes, in retrospect I should've probably checked around whether this
process has been successful for others.. but that's why they say
hindsight is 20/20
next reply other threads:[~2010-07-19 0:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 0:32 Konstantin Svist [this message]
2010-07-19 0:41 ` messed up changing chunk size Steven Haigh
2010-07-19 0:51 ` Konstantin Svist
2010-07-19 1:29 ` Guy Watkins
2010-07-19 1:45 ` Konstantin Svist
2010-07-19 1:51 ` Guy Watkins
2010-07-19 3:53 ` Roman Mamedov
2010-07-19 13:24 ` Jools Wills
2010-07-19 14:58 ` Roman Mamedov
2010-07-19 19:02 ` Keld Simonsen
2010-07-19 18:04 ` Konstantin Svist
2010-07-20 4:28 ` Konstantin Svist
2010-07-20 6:29 ` Konstantin Svist
2010-07-20 16:30 ` [SOLVED] " Konstantin Svist
2010-07-20 17:01 ` Konstantin Svist
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=4C439D19.4070906@gmail.com \
--to=fry.kun@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.