From: NeilBrown <neilb@suse.de>
To: "Vanhorn, Mike" <michael.vanhorn@wright.edu>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: md raid6 not working
Date: Wed, 22 Aug 2012 08:38:24 +1000 [thread overview]
Message-ID: <20120822083824.4dc16431@notabene.brown> (raw)
In-Reply-To: <429D03F4F1CC234886D1288428CFE8E0D42B0E@CH1PRD0102MB110.prod.exchangelabs.com>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
On Tue, 21 Aug 2012 11:17:57 +0000 "Vanhorn, Mike"
<michael.vanhorn@wright.edu> wrote:
> Thank you for your response. Here is the output you requested.
>
> >What is the result of:
> >
> > mdadm -S /dev/md0
>
> # mdadm -S /dev/md0
> mdadm: stopped /dev/md0
> #
>
> > mdadm -Avvv /dev/md0
>
> # mdadm -Avvv /dev/md0
> mdadm: looking for devices for /dev/md0
> mdadm: cannot open device /dev/sdi1: Device or resource busy
> mdadm: /dev/sdi1 has no superblock - assembly aborted
> #
So /dev/sdi1 is busy. You need to find out why. (the "no superblock"
message is a bit misleading... I might have fixed that in newer mdadm, I'm
not sure).
The "/proc/mdstat" that you showed in the original email had sdi1 as a member
of md0, so it clearly wasn't being used by anything else then.
"mdadm -S /dev/md0" would have removed it from md0 so it shouldn't have been
busy.
The fact that it is busy is very odd.
A device can be busy if:
- it is mounted as a filesystem
- it is active as swap
- it is part of an md array
- it is part of a dm device
- probably something else, but those are the main ones.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-08-21 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 19:06 md raid6 not working Vanhorn, Mike
2012-08-20 22:34 ` NeilBrown
2012-08-21 11:17 ` Vanhorn, Mike
2012-08-21 22:38 ` NeilBrown [this message]
2012-08-22 12:57 ` Vanhorn, Mike
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=20120822083824.4dc16431@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=michael.vanhorn@wright.edu \
/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).