From: Wade Pinkston <blata@bugs.osu.edu>
To: linux-raid@vger.kernel.org
Subject: Re: raid not creating
Date: Sun, 29 Jan 2006 18:29:59 -0800 [thread overview]
Message-ID: <43DD7A27.6070806@bugs.osu.edu> (raw)
In-Reply-To: <17373.14913.427109.184586@cse.unsw.edu.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Neil Brown wrote:
> On Friday January 27, blata@bugs.osu.edu wrote:
>
> Please don't take a discussion off a mailing list once it has started
> there. Other people might be listening, and it is useful to have any
> answers in the archives.
>
> So if you want further help on this, please continue to send your mail
> to linux-raid@vger.kernel.org.
>
> NeilBrown
>
>
>
>
>
> Neil Brown wrote:
>
>>On Friday January 27, blata@bugs.osu.edu wrote:
>
>
>>># mdadm --create --verbose /dev/md4 --level=1 --raid-devices=2 /dev/hde3
>>>/dev/hdg3
>>>mdadm: /dev/hde3 appears to contain an ext2fs file system
>>> size=35214480K mtime=Thu Jan 26 13:38:20 2006
>>>mdadm: /dev/hdg3 appears to contain an ext2fs file system
>>> size=35214480K mtime=Thu Jan 26 13:38:20 2006
>>>mdadm: size set to 35214400K
>>>Continue creating array? y
>>>mdadm: SET_ARRAY_INFO failed for /dev/md4: Device or resource busy
>
>
>>Sounds like /dev/md4 already exists. What does
>> cat /proc/mdstat
>>show?
>
>>NeilBrown
>
>
> cat /proc/mdstat
> Personalities :
> md2 : inactive hdc3[0]
> 8723200 blocks
> md3 : inactive hdg1[0]
> 61440448 blocks
> md4 : inactive hdg3[0]
> 35214400 blocks
> md1 : inactive hdc2[0]
> 20482752 blocks
> md0 : inactive hdc1[0]
> 104320 blocks
> unused devices: <none>
>
> I got this only after doing the following.
>
> mdadm --manage --add /dev/md2 /dev/hdc3
>
> for each md device. If I then go back and try to add /dev/hda1 to the md0
> I get this.
>
> mdadm --manage --add /dev/md0 /dev/hda1
> mdadm: add new device failed for /dev/hda1: Device or resource busy
>
> this email includes all new informaiton for me. but I still am unable to
> add the drives with the actual data on them.
>
sorry didn't realize just responding took the tread off list.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFD3Xonv+6+qSFv3TURAuKiAJ9nIYIcWcRfUycNGLg49H7WIKbIBgCgpKte
R+zZ9W1/KAJH4If+ncNdo5E=
=/n3B
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-01-30 2:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 17:35 raid not creating Wade Pinkston
2006-01-27 21:10 ` Neil Brown
[not found] ` <43DAD418.9040803@bugs.osu.edu>
[not found] ` <17373.14913.427109.184586@cse.unsw.edu.au>
2006-01-30 2:29 ` Wade Pinkston [this message]
2006-01-30 3:08 ` Neil Brown
2006-01-30 5:02 ` Wade Pinkston
2006-01-30 5:17 ` Neil Brown
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=43DD7A27.6070806@bugs.osu.edu \
--to=blata@bugs.osu.edu \
--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).