Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "TJ Harrell" <systemloc@earthlink.net>
To: linux-raid@vger.kernel.org
Subject: raidreconf won't resize a RAID 5 array. Can it be done with mkraid -f ?
Date: Mon, 17 May 2004 11:08:53 -0400	[thread overview]
Message-ID: <000901c43c20$df38fb10$0201a8c0@windows> (raw)

I have a raid 5 array consisting of 3 disks. The smallest disk is 195191168
blocks. The array only uses 172551296 blocks from each device. Numbers ar
from output of mdadm. I would like to grow the array to the largest
posssible size. I tried doing a raidreconf using identical settings in
raidtab.old and raidtab.new, and it said the size would remain unchanged
when it asked for confirmation. Is there a way to tweak it to do what I
want, or could I just mkraid -f the existing array? I'm afraid if I just do
a mkraid -f it will fubar the old array by laying out parity info
differently or something since the size of the array will be different.

Raidtab:
raiddev /dev/md0
   raid-level      linear
   nr-raid-disks      3
   persistent-superblock   1
   chunk-size      128

device      /dev/hdk1
raid-disk   0
device      /dev/hdi1
raid-disk   1
device      /dev/hda3
raid-disk   2

raiddev /dev/md1
   raid-level      5
   nr-raid-disks      3
   persistent-superblock   1
   chunk-size      64

device      /dev/hdg1
raid-disk   0
device      /dev/md0
failed-disk 1
device      /dev/hdc1
raid-disk   2


Output of "raidreconf -o /etc/raidtab -n /etc/raidtab.new -m /dev/md1"

Working with device /dev/md1
Parsing /etc/raidtab
Parsing /etc/raidtab.new
Size of old array: 1171815940 blocks,  Size of new array: 1171815940 blocks
Old raid-disk 0 has 3052474 chunks, 195358336 blocks
Old raid-disk 1 has 3049861 chunks, 195191104 blocks
Old raid-disk 2 has 3052474 chunks, 195358336 blocks
New raid-disk 0 has 3052474 chunks, 195358336 blocks
New raid-disk 1 has 3049861 chunks, 195191104 blocks
New raid-disk 2 has 3052474 chunks, 195358336 blocks
Using 64 Kbyte blocks to move from 64 Kbyte chunks to 64 Kbyte chunks.
Detected 418432 KB of physical memory in system
A maximum of 1394 outstanding requests is allowed
---------------------------------------------------
I will convert your old device /dev/md1 of 6102335 blocks
to a new device /dev/md1 of same size
using a block-size of 64 KB
Is this what you want? (yes/no): no



             reply	other threads:[~2004-05-17 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 15:08 TJ Harrell [this message]
2004-05-17 20:28 ` raidreconf won't resize a RAID 5 array. Can it be done with mkraid -f ? Guy
2004-05-17 20:59   ` TJ Harrell

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='000901c43c20$df38fb10$0201a8c0@windows' \
    --to=systemloc@earthlink.net \
    --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