From: Jim <jim@fayettedigital.com>
To: linux-raid@vger.kernel.org
Subject: Re: Raid 1, can't get the second disk added back in.
Date: Mon, 07 Jan 2008 09:26:12 -0500 [thread overview]
Message-ID: <47823684.80501@fayettedigital.com> (raw)
In-Reply-To: <18305.22361.482483.331552@notabene.brown>
Neil Brown wrote:
> On Saturday January 5, jim@fayettedigital.com wrote:
>
>> root@chinaberry:~# mdadm /dev/md0 --add /dev/hdb5
>> mdadm: Cannot open /dev/hdb5: Device or resource busy
>>
>> All the solutions I've been able to google fail with the busy. There is
>> nothing that I can find that might be using /dev/hdb5 except the raid
>> device and it appears it's not either.
>>
>
> Very odd. But something must be using it.
>
> What does
> ls -l /sys/block/hdb/hdb5/holders
> show?
> What about
> cat /proc/mounts
> cat /proc/swaps
> lsof /dev/hdb5
>
> ??
> NeilBrown
> -
> 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
>
>
I agree but for the life of me I can't figure out what, other than some
raid daemon.
root@chinaberry:~# ls -l /sys/block/hdb/hdb5/holders
total 0
root@chinaberry:~# cat /proc/mounts
none /sys sysfs rw,nosuid,nodev,noexec 0 0
none /proc proc rw,nosuid,nodev,noexec 0 0
udev /dev tmpfs rw 0 0
/dev/disk/by-uuid/4f67dae8-cdcb-460e-86cd-a5f0e4009422 / ext3
rw,data=ordered 0 0
/dev/disk/by-uuid/4f67dae8-cdcb-460e-86cd-a5f0e4009422 /dev/.static/dev
ext3 rw,data=ordered 0 0
tmpfs /var/run tmpfs rw,nosuid,nodev,noexec 0 0
tmpfs /var/lock tmpfs rw,nosuid,nodev,noexec 0 0
tmpfs /dev/shm tmpfs rw 0 0
devpts /dev/pts devpts rw 0 0
usbfs /dev/bus/usb/.usbfs usbfs rw 0 0
udev /proc/bus/usb tmpfs rw 0 0
usbfs /proc/bus/usb/.usbfs usbfs rw 0 0
tmpfs /var/run tmpfs rw,nosuid,nodev,noexec 0 0
tmpfs /var/lock tmpfs rw,nosuid,nodev,noexec 0 0
/dev/sda5 /home ext3 rw,data=ordered 0 0
/dev/md0 /backupmirror ext3 rw,data=ordered 0 0
/dev/hda1 /vz ext3 rw,data=ordered 0 0
/vz/private/225 /vz/root/225 simfs rw 0 0
/vz/private/300 /vz/root/300 simfs rw 0 0
/proc /vz/root/225/proc proc rw 0 0
/sys /vz/root/225/sys sysfs rw 0 0
none /vz/root/225/dev/pts devpts rw 0 0
/proc /vz/root/300/proc proc rw 0 0
/sys /vz/root/300/sys sysfs rw 0 0
none /vz/root/300/dev/pts devpts rw 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
root@chinaberry:~# cat /proc/mounts | grep hdb
root@chinaberry:~# cat /proc/swaps
root@chinaberry:~# lsof /dev/hdb5
next prev parent reply other threads:[~2008-01-07 14:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 16:05 Raid 1, can't get the second disk added back in Jim
2008-01-05 20:00 ` Nagilum
2008-01-06 11:13 ` Jim
2008-01-06 16:31 ` Nagilum
2008-01-06 16:49 ` Jim
2008-01-06 22:28 ` Neil Brown
2008-01-06 22:34 ` Neil Brown
2008-01-07 14:26 ` Jim [this message]
2008-01-07 14:46 ` Jim
2008-01-07 22:47 ` Neil Brown
2008-01-08 21:02 ` Bill Davidsen
2008-01-10 6:25 ` dean gaudet
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=47823684.80501@fayettedigital.com \
--to=jim@fayettedigital.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).