From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: linux-raid@vger.kernel.org
Subject: Kernel 2.6.17 and RAID5 Grow Problem (critical section backup)
Date: Fri, 7 Jul 2006 08:38:08 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0607070830450.2648@p34.internal.lan> (raw)
p34:~# mdadm /dev/md3 -a /dev/hde1
mdadm: added /dev/hde1
p34:~# mdadm -D /dev/md3
/dev/md3:
Version : 00.90.03
Creation Time : Fri Jun 30 09:17:12 2006
Raid Level : raid5
Array Size : 1953543680 (1863.04 GiB 2000.43 GB)
Device Size : 390708736 (372.61 GiB 400.09 GB)
Raid Devices : 6
Total Devices : 7
Preferred Minor : 3
Persistence : Superblock is persistent
Update Time : Fri Jul 7 08:25:44 2006
State : clean
Active Devices : 6
Working Devices : 7
Failed Devices : 0
Spare Devices : 1
Layout : left-symmetric
Chunk Size : 512K
UUID : e76e403c:7811eb65:73be2f3b:0c2fc2ce
Events : 0.232940
Number Major Minor RaidDevice State
0 22 1 0 active sync /dev/hdc1
1 56 1 1 active sync /dev/hdi1
2 3 1 2 active sync /dev/hda1
3 8 49 3 active sync /dev/sdd1
4 88 1 4 active sync /dev/hdm1
5 8 33 5 active sync /dev/sdc1
6 33 1 - spare /dev/hde1
p34:~# mdadm --grow /dev/md3 --raid-disks=7
mdadm: Need to backup 15360K of critical section..
mdadm: Cannot set device size/shape for /dev/md3: No space left on device
p34:~# mdadm --grow /dev/md3 --bitmap=internal --raid-disks=7
mdadm: can change at most one of size, raiddisks, bitmap, and layout
p34:~# umount /dev/md3
p34:~# mdadm --grow /dev/md3 --raid-disks=7
mdadm: Need to backup 15360K of critical section..
mdadm: Cannot set device size/shape for /dev/md3: No space left on device
p34:~#
The disk only has about 350GB of 1.8TB used, any idea why I get this
error?
I searched google but could not find anything on this issue when trying to
grow the array?
next reply other threads:[~2006-07-07 12:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 12:38 Justin Piszcz [this message]
2006-07-07 12:46 ` Justin Piszcz
2006-07-07 12:49 ` Justin Piszcz
2006-07-07 14:37 ` Justin Piszcz
2006-07-07 19:04 ` Justin Piszcz
2006-07-07 19:42 ` Justin Piszcz
2006-07-07 22:00 ` Neil Brown
2006-07-07 22:15 ` Justin Piszcz
2006-07-07 22:31 ` Neil Brown
2006-07-07 22:35 ` Justin Piszcz
2006-07-07 22:38 ` Neil Brown
2006-07-07 22:39 ` Justin Piszcz
2006-07-10 21:47 ` Justin Piszcz
2006-07-10 22:27 ` Jan Engelhardt
2006-07-10 22:30 ` Justin Piszcz
2006-07-11 7:52 ` Jan Engelhardt
2006-07-11 9:05 ` Petr Vyskocil
2006-07-18 0:16 ` Neil Brown
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=Pine.LNX.4.64.0607070830450.2648@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®