All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Arthur Oehser <tom@toms.net>
To: linux-raid@vger.kernel.org
Subject: Re: Is shrinking raid5 possible?
Date: Fri, 6 Nov 2009 08:17:40 -0500	[thread overview]
Message-ID: <20091106131740.GA30506@Toms.NET> (raw)
In-Reply-To: <4564B5C3.9050501@idgmail.se>


> > 2) One wants to do something else with some of the space, although for
> > a RAID5 I don't quite see the point - you'd end up with n small
> > partitions. Shrinking a 2-way mirror or stripe this way sounds far
> > more useful.

Oooh, what would I want to do with "n small partitions"?  I know!  Raid!

Scenario:

existing:
sda1 sdb1 sdc1 254M + 254M + 254M = 254M raid-1 /boot
sda2 sdb2 sbc2 2G + 2G + 2G = 6G raid-0 swap
sda3 sdb3 sdc3 1.5T + 1.5T + 15.T = 3T raid-5 /

desired:
sda1 sdb1 sdc1 254M + 254M + 254M = 254M raid-1 /dev/md1 /boot
sda2 sdb2 sbc2 2G + 2G + 2G = 6G raid-0 swap /dev/md2
sda3 sdb3 sdc3 1.4T + 1.4T + 1.4T = 2.8T raid-5 /dev/md3 /
sda4 sdb4 sdc4 100G + 100G + 100G = 200G raid-5 /dev/md4 / <= alt for Koala

Since /dev/md3 is still only 70% full, I thought I could do something like:

 - resize2fs /dev/md3 <smaller>
 - mdadm -G -z <smaller> /dev/md3
 - fdisk /dev/sd[a-c]3 <smaller>

It _almost_ works fine... but... the mdadm -G keeps the (0.90) superblock
at the _end_ of the _device_ ... which hasn't been resized yet ...

How do I put the superblock back after fdisk, or make -G move or recreate?

-Tom


  reply	other threads:[~2009-11-06 13:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19  2:30 Is shrinking raid5 possible? Paul Davidson
2006-06-19  4:39 ` Neil Brown
2006-06-19  5:07   ` Paul Davidson
2006-06-23  0:49   ` Bill Davidsen
2006-06-23  1:26     ` Neil Brown
2006-06-23  2:17       ` Paul Davidson
2006-06-23  8:34       ` Henrik Holst
2006-06-23 18:16       ` Christian Pernegger
2006-06-26  7:41         ` Neil Brown
2006-06-26 11:33           ` Christian Pernegger
2006-11-22 20:40             ` Henrik Holst
2009-11-06 13:17               ` Thomas Arthur Oehser [this message]
2009-11-06 15:04                 ` Asdo
2009-11-06 15:26                   ` Thomas Arthur Oehser
2009-11-06 17:00                     ` Goswin von Brederlow
2009-11-06 18:32                 ` John Robinson
2009-11-06 18:38                   ` Thomas Arthur Oehser
2009-11-06 19:30                     ` Goswin von Brederlow
2009-11-06 19:38                       ` John Robinson

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=20091106131740.GA30506@Toms.NET \
    --to=tom@toms.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 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.