From: Nate Byrnes <nate@qabal.org>
Cc: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: RAID5 recovery trouble, bd_claim failed?
Date: Mon, 17 Apr 2006 15:29:34 -0400 [thread overview]
Message-ID: <4443EC9E.9010502@qabal.org> (raw)
In-Reply-To: <444386C6.2070201@qabal.org>
Hi Neil, List,
Am I just out of luck? Perhaps a full reboot? Something else?
Thanks,
Nate
Nate Byrnes wrote:
> Hi Neil,
> Nothing references hdf as you can see below. I have also rmmod'ed
> md and raid5 modules and modprobed them back in. Thoughts?
>
> Thanks again,
> Nate
>
> root@finn:~# cat /proc/swaps
> Filename Type Size
> Used Priority
> /dev/sdb2 partition 1050616
> 1028 -1
>
> root@finn:~# cat /proc/mounts
> rootfs / rootfs rw 0 0
> /dev/root / ext3 rw 0 0
> proc /proc proc rw,nodiratime 0 0
> sysfs /sys sysfs rw 0 0
> none /dev ramfs rw 0 0
> /dev/sdb1 /usr ext3 rw 0 0
> devpts /dev/pts devpts rw 0 0
> nfsd /proc/fs/nfsd nfsd rw 0 0
> usbfs /proc/bus/usb usbfs rw 0 0
>
> root@finn:~# cat /proc/mdstat
> Personalities : [raid5]
> md0 : inactive hdh[2] hdg[3] hde[1]
> 234451968 blocks
>
> unused devices: <none>
>
>
> Neil Brown wrote:
>> On Monday April 17, nate@qabal.org wrote:
>>
>>>> What is /dev/hdf busy? Is it in use? mounted? something?
>>>>
>>>>
>>> Not that I am aware of. Here is the mount output:
>>>
>>> root@finn:/etc# mount
>>> /dev/sda1 on / type ext3 (rw)
>>> proc on /proc type proc (rw)
>>> sysfs on /sys type sysfs (rw)
>>> /dev/sdb1 on /usr type ext3 (rw)
>>> devpts on /dev/pts type devpts (rw,gid=5,mode=620)
>>> nfsd on /proc/fs/nfsd type nfsd (rw)
>>> usbfs on /proc/bus/usb type usbfs (rw)
>>>
>>> lsof | grep hdf does not return any results.
>>>
>>> is there some other way to find out?
>>>
>>
>> cat /proc/swaps
>> cat /proc/mounts
>> cat /proc/mdstat
>>
>> as well as 'lsof' should find it.
>>
>> -
>> 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
>>
>>
>>
>>
>
> !DSPAM:444386c978211215816793!
>
next prev parent reply other threads:[~2006-04-17 19:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 13:01 RAID5 recovery trouble, bd_claim failed? Nathanial Byrnes
2006-04-16 22:46 ` Neil Brown
2006-04-17 2:54 ` Nathanial Byrnes
2006-04-17 3:04 ` Neil Brown
2006-04-17 10:08 ` Nathanial Byrnes
2006-04-17 10:29 ` Neil Brown
2006-04-17 12:15 ` Nate Byrnes
2006-04-17 19:29 ` Nate Byrnes [this message]
2006-04-17 21:43 ` Neil Brown
2006-04-17 22:21 ` Nathanial Byrnes
2006-04-18 0:24 ` Neil Brown
2006-04-18 10:07 ` Nathanial Byrnes
2006-04-18 22:13 ` Maurice Hilarius
2006-04-18 23:39 ` Nathanial Byrnes
2006-04-19 13:41 ` Maurice Hilarius
2006-04-19 13:53 ` Nate Byrnes
2006-04-19 14:04 ` Maurice Hilarius
2006-04-19 14:20 ` Nate Byrnes
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=4443EC9E.9010502@qabal.org \
--to=nate@qabal.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).