linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Brancato <mike@mikebrancato.com>
To: David Lethe <david@santools.com>
Cc: Alex Lilley <alex@redwax.co.uk>, linux-raid@vger.kernel.org
Subject: Re: status of raid 4/5 disk reduce
Date: Thu, 11 Dec 2008 01:33:51 -0500	[thread overview]
Message-ID: <4940B44F.9000000@mikebrancato.com> (raw)
In-Reply-To: <A20315AE59B5C34585629E258D76A97C02FA1D78@34093-C3-EVS3.exchange.rackspace.com>


David Lethe wrote:

>   
> Respectfully, go bother the LVM, jfs, ext, afs, and all the other file
> system people.  You have zero chance of getting them on board to support
> online file system shrinking without any guarantee of scratch space.
> My advice is that you don't tell them you also want them to resize while
> the md volume is being resized, and also don't tell them that the array
> might be degraded.

I didn't bring up nor argued the filesystem online resize issue, you 
did.  Why does the filesystem have to be online during the reshape or 
the shrink?  People shrink filesystems and partitions while offline 
everyday, and the sun still rises.  Filesystem support for reshaping 
(not resizing) should be a non-issue.  Resizing shrink exists today.

> If you want to copy 4x120 into 3x500 ... mount all the disks and COPY
> the data.  If you are truly limited to 4 disks, and are too cheap to
> spend $10-20 for another controller, after buying 1.5TB worth of disk
> drives, then you really need to get your priorities in order.

Words fail me....  Why support reshaping RAID arrays by adding disks 
then if we should just go buy more disks and create a new array to copy 
the data to?

I don't know why you oppose the flexibility of reshape shrinking, but at 
one point it was planned.  I simply tried to see what the status was of 
the development and what was needed to get support for reshape shrink. 
When it comes to actually using it, to each his own.

  reply	other threads:[~2008-12-11  6:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08 20:59 status of raid 4/5 disk reduce Michael Brancato
2008-12-09 21:11 ` Alex Lilley
2008-12-09 21:33   ` David Lethe
2008-12-09 21:51     ` Robin Hill
2008-12-09 23:15       ` Ryan Wagoner
2008-12-10 12:14         ` Alex Lilley
2008-12-11  0:07           ` Michael Brancato
2008-12-11  4:30             ` David Lethe
2008-12-11  6:33               ` Michael Brancato [this message]
2008-12-11 13:52                 ` Louis-David Mitterrand
2008-12-11 15:13                   ` Michael Brancato
2008-12-11 11:43               ` John Robinson
2008-12-11 14:46                 ` Mikael Abrahamsson
2008-12-11 15:24                   ` David Lethe
2008-12-11 16:13                     ` Michael Brancato
2008-12-11 15:27                   ` Michael Brancato
2008-12-11 11:51               ` Alex Lilley
2008-12-15 23:18 ` Neil Brown
  -- strict thread matches above, loose matches on Subject: below --
2008-12-12 15:38 David Lethe

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=4940B44F.9000000@mikebrancato.com \
    --to=mike@mikebrancato.com \
    --cc=alex@redwax.co.uk \
    --cc=david@santools.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 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).