linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jeremy Leigh" <jeremy.leigh@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Problem Growing Raid 5 Array - Help Needed!
Date: Tue, 3 Jun 2008 00:50:35 +1000	[thread overview]
Message-ID: <484408bf.20018e0a.68db.ffffe97f@mx.google.com> (raw)

Hi Guys, I have just grown my raid 5 from 7 to 8 500Gb drives.
I am now running into this problem.
When I try to run fsck /dev/md0 I get the following:

fsck.ext2: Device or resource busy while trying to open /dev/md0
Filesystem mounted or opened exclusively by another program?

Or when I try to run resize2fs /dev/md0 to make use of new drive, I get the
following:

resize2fs: Device or resource busy while trying to open /dev/md0
Couldn’t find valid filesystem superblock.

Cat /proc/mdstat outputs:

Personalities : [raid6] [raid5] [raid4] 
md0 : active raid5 sdb1[0] sdi1[7] sdg1[6] sdh1[5] sdf1[4] sde1[3] sdd1[2]
sdc1[1]
      3418686208 blocks level 5, 256k chunk, algorithm 2 [8/8] [UUUUUUUU]
      
unused devices: <none>

However, I can still access and mount my filesystem - I just cannot grow it,
which I find very strange.
I have tried to init 1, to go to single user mode, and I have made sure file
system is unmounted, but this ‘busy’ error still occurs.

Any ideas? I’m kinda stuck. Google is no help!

I am running fedora core 7.

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2008-06-02 14:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 14:50 Jeremy Leigh [this message]
2008-06-02 15:13 ` Problem Growing Raid 5 Array - Help Needed! David Greaves
2008-06-03 15:03   ` Jeremy Leigh
2008-06-03 16:50     ` David Greaves
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=484408bf.20018e0a.68db.ffffe97f@mx.google.com \
    --to=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 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).