From: rrk <rrk@prairie.lakes.com>
To: linux-raid@vger.kernel.org
Subject: Re: Raid1 problem can't add remove or mark faulty -- it did work
Date: Sun, 27 Mar 2005 13:30:29 -0600 [thread overview]
Message-ID: <424709D5.5060105@prairie.lakes.com> (raw)
In-Reply-To: <200503271903.j2RJ3cT03030@www.watkins-home.com>
Guy wrote:
>I am not sure what bd_claim is, but it is somewhat like open(). My guess is
>your disk is in use, maybe nounted. Run this command and send the output.
>
>df
>
>Guy
>
>
>
yep that was it -- there is a whizzing wizard somewhere it is not
fstab-- though i checked that
sorry for the trouble and thanks
rob
>
>
>>-----Original Message-----
>>From: linux-raid-owner@vger.kernel.org [mailto:linux-raid-
>>owner@vger.kernel.org] On Behalf Of rrk
>>Sent: Sunday, March 27, 2005 1:38 PM
>>To: linux-raid@vger.kernel.org
>>Subject: Raid1 problem can't add remove or mark faulty -- it did work
>>
>>@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>>mdstat after reboot
>>
>>root@crm_svr:~# cat /proc/mdstat
>>Personalities : [linear] [raid0] [raid1] [raid5] [multipath] [raid6]
>>[raid10]
>>md0 : active raid1 hdc1[1]
>> 155268096 blocks [2/1] [_U]
>>
>>unused devices: <none>
>>
>>@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>>the below error shows after a boot when excuted in kde konsole
>>
>>root@crm_svr:/home/rob# mdadm /dev/md0 -a /dev/hda1
>>mdadm: hot add failed for /dev/hda1: Invalid argument
>>
>>but this error is shown from a tty console
>>
>>md: could not bd_claim hda1
>>md: error, md_import_device() returned -16
>>mdadm: hot add failed for /dev/hda1 : invalid argument
>>
>>@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>>this is what shows in dmesg
>>
>>md: could not bd_claim hda1.
>>md: error, md_import_device() returned -16
>>md: could not bd_claim hda1.
>>md: error, md_import_device() returned -16
>>md: could not bd_claim hda1.
>>md: error, md_import_device() returned -16
>>
>>i had this bd_claim error when i first tried to build the array
>>but it went away when i wiped every thing and started over
>>this box is the only time i have seen this error and i
>>tried using different drives -- but of the same type -- when
>>the problem showed up on the initial build
>>
>>
>>
>>
>>-
>>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
>>
>>
>
>-
>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
>
>
>
>
next prev parent reply other threads:[~2005-03-27 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 18:38 Raid1 problem can't add remove or mark faulty -- it did work rrk
2005-03-27 19:03 ` Guy
2005-03-27 19:30 ` rrk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-27 2:36 rrk
2005-03-27 7:26 ` 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=424709D5.5060105@prairie.lakes.com \
--to=rrk@prairie.lakes.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.