All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: NeilBrown <neilb@suse.com>
Cc: Phil Turmel <philip@turmel.org>, John Stoffel <john@stoffel.org>,
	Eli Ben-Shoshan <eli@benshoshan.com>,
	Jes.Sorensen@gmail.com, linux-raid@vger.kernel.org
Subject: Re: mdadm: Patch to restrict --size when shrinking unless forced
Date: Tue, 10 Oct 2017 16:55:57 -0400	[thread overview]
Message-ID: <20171010205557.GA11500@animx.eu.org> (raw)
In-Reply-To: <87y3oiwws3.fsf@notabene.neil.brown.name>

NeilBrown wrote:
> On Mon, Oct 09 2017, Wakko Warner wrote:
> 
> > Phil Turmel wrote:
> >> A certain amount of the trouble with all of this is the english meaning
> >> of "grow" doesn't really match what mdadm allows.
> >> 
> >> Might it be reasonable to reject "--grow" operations that reduce the
> >> final array size, and introduce the complementary "--reduce" operation
> >> that rejects array size increases?
> >> 
> >> Both operations would share the current code, just apply a different
> >> sanity check before proceeding.
> >> 
> >> mdadm would then at least not violate the rule of least surprise.
> >
> > As a general user of md raid and as a reader of the list, I would agree that
> > this would be a better solution.  Thinking in terms of lvm, there's lvreduce
> > and lvextend.  IMO, --force wouldn't be needed for --reduce (I was orginally
> > thinking of --shrink)
> >
> > On a side note, is it possible for the lower layers to know what the last
> > used sector is?  IE lvm ontop of raid and has 10% allocated and the last
> > sector is around the 10% mark.  (If this were possible --force would be,
> > required if shrinking would result in inaccessible data)
> 
> No it isn't.  I've occasionally thought of adding functionality so that
> the a device could ask its client (e.g. filesystem, lvm, etc) if
> shrinking is OK - but it hasn't happened yet.

That's what I thought but wasn't sure.  Thanks.

> > I recently did a shrink of 4x 2tb drives so that I could replace the 2tb
> > drives with 80gb drives (yes, big shrink!)  Would have been nice for mdadm
> > to know the smallest size was that wouldn't destroy my lvm volumes that were
> > on top.
> 
> Guess, try, see if data is still accessible.  If not, revert the change.
> If you have a filesystem on the raid, fsck will complain if you made it
> too small.  I don't know what you would try with lvm.  pvscan?

Fortunately for me, my first try worked.

-- 
 Microsoft has beaten Volkswagen's world record.  Volkswagen only created 22
 million bugs.

  reply	other threads:[~2017-10-10 20:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04 18:00 mdadm: Patch to restrict --size when shrinking unless forced John Stoffel
2017-10-04 18:11 ` Jes Sorensen
2017-10-04 19:15   ` John Stoffel
2017-10-04 19:23     ` Jes Sorensen
2017-10-04 19:33       ` John Stoffel
2017-10-04 21:50 ` NeilBrown
2017-10-05  1:26   ` John Stoffel
2017-10-07 22:06     ` Wols Lists
2017-10-07 22:17       ` John Stoffel
2017-10-07 22:37         ` Wols Lists
2017-10-07 22:46           ` John Stoffel
2017-10-08 20:57   ` John Stoffel
2017-10-08 22:52     ` NeilBrown
2017-10-09  1:18       ` John Stoffel
2017-10-09  1:36         ` NeilBrown
2017-10-09  1:22       ` John Stoffel
2017-10-09  4:10         ` NeilBrown
2017-10-09 20:04           ` Phil Turmel
2017-10-10  0:07             ` Wakko Warner
2017-10-10 13:12               ` Phil Turmel
2017-10-10 20:52               ` NeilBrown
2017-10-10 20:55                 ` Wakko Warner [this message]
2017-10-10  2:01             ` John Stoffel
2017-10-10 20:09             ` Jes Sorensen
2017-10-10 20:54               ` Wols Lists
2017-10-10 21:07                 ` Jes Sorensen
2017-10-10 20:48             ` NeilBrown
2017-10-10 20:58               ` Phil Turmel

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=20171010205557.GA11500@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=Jes.Sorensen@gmail.com \
    --cc=eli@benshoshan.com \
    --cc=john@stoffel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.com \
    --cc=philip@turmel.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.