All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: Jeremy Leigh <jeremy.leigh@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Problem Growing Raid 5 Array - Help Needed!
Date: Tue, 03 Jun 2008 17:50:47 +0100	[thread overview]
Message-ID: <48457667.9030103@dgreaves.com> (raw)
In-Reply-To: <48455d39.16078e0a.20d2.14eb@mx.google.com>

Jeremy Leigh wrote:
> Hi David,
> Mount works fine for the LVM volume sitting on /dev/md0
> [root@FileServer ~]# mount /dev/LVMRAID/LV0 /home

Ah...

lvm is holding /dev/md0 open.

lvm is layered on top of, and uses, md - just like md uses your hard disks.

Try:
  /etc/init.d/lvm2 stop

That should do it.


> Finally, I can give you output of mdadm --detail, but to be honest, I don't
> know what else I can do... This is really frustrating.
It would be nice if something told you what was holding the lock.
I occasionally forget on the server that uses lvm.

> These commands are being run from root.
>
> [root@FileServer ~]# fsck /dev/md0
Yeah - that's a bad idea!!!
your filesystem lives on /dev/LVMRAID/LV0
  fsck /dev/LVMRAID/LV0

If you had been really unlucky, fsck could have found a superblock and started
scribbling all over your filesystem with potentially devastating results!
Always run filesystem tools on the device holding the filesystem, rather than
some random component ;)

and similartly
> [root@FileServer ~]# resize2fs /dev/md0
resize2fs /dev/LVMRAID/LV0

HTH

David

  reply	other threads:[~2008-06-03 16:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 14:50 Problem Growing Raid 5 Array - Help Needed! Jeremy Leigh
2008-06-02 15:13 ` David Greaves
2008-06-03 15:03   ` Jeremy Leigh
2008-06-03 16:50     ` David Greaves [this message]
2008-06-06 12:39       ` Jeremy Leigh

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=48457667.9030103@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=jeremy.leigh@gmail.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.