All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID5 won't mount after reducing disks from 8 to 6
Date: Wed, 16 Feb 2011 21:06:40 -0600	[thread overview]
Message-ID: <4D5C90C0.6040607@hardwarefreak.com> (raw)
In-Reply-To: <20110217131453.39444287@notabene.brown>

NeilBrown put forth on 2/16/2011 8:14 PM:

> So your best bet it to convince xfs_repair to work with what you've got and
> try to knit together as much as it can  - which may be nothing, I really
> don't know.

xfs_repair won't help.  He's hosed.  If this had been a grow from 8
disks to 10 he'd be ok, as you grow mdadm first then XFS.  But as I
said, XFS has no shrink capability.  xfs_repair will just puke all over
itself if you run it.

> Maybe you could ask on an XFS list somewhere.

He already did, in a way, as I'm on that list.  You're more than welcome
to ask on the XFS mailing list, but you'll get the same answer.

This really sucks and I feel for Matt.  I wish he'd have asked on either
or both lists first...

What he needs to do now is start over from scratch.  Delete the current
md device and create a new one, then create a new XFS filesystem, and
then restore his files from his backup device.

Is there a Linux mdraid best practices document somewhere, that could
help prevent folks from hosing themselves like this if they'd read it first?

-- 
Stan

  parent reply	other threads:[~2011-02-17  3:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17  0:24 RAID5 won't mount after reducing disks from 8 to 6 Matt Tehonica
2011-02-17  1:30 ` Phil Turmel
2011-02-17  1:39   ` Matt Tehonica
2011-02-17  2:13     ` Phil Turmel
2011-02-17  2:18   ` Keld Jørn Simonsen
2011-02-17  2:43   ` Stan Hoeppner
2011-02-17  1:42 ` NeilBrown
2011-02-17  1:47   ` Matt Tehonica
2011-02-17  2:14     ` NeilBrown
2011-02-17  2:22       ` Matt Tehonica
2011-02-17  3:06       ` Stan Hoeppner [this message]
2011-02-17  3:11     ` Joe Landman

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=4D5C90C0.6040607@hardwarefreak.com \
    --to=stan@hardwarefreak.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 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.