From: Derek Vadala <derek@cynicism.com>
To: linux-raid@vger.kernel.org
Cc: Scott Walter <walter@cognigencorp.com>
Subject: Re: Raidstop /dev/md0 won't work
Date: Thu, 2 May 2002 14:52:05 -0700 (PDT) [thread overview]
Message-ID: <Pine.GSO.4.21.0205021450480.18460-100000@gecko.roadtoad.net> (raw)
In-Reply-To: <3CD1AF20.45E85EC8@cognigencorp.com>
On Thu, 2 May 2002, Scott Walter wrote:
> this is probably a very dumb question.. however I am not able to
> raidstop my raid-array using, which i need to do before running
> raidreconf.
>
> %> raidstop /dev/md0
> /dev/md0: Device or resource busy.
> %>
try doing fuser -m on /dev/md0 to see which processes are using it...
# fuser -m /dev/md0
/dev/md0: 8685c
then us ps to figure out what's up
---
Derek Vadala, derek@cynicism.com, http://www.cynicism.com/~derek
next prev parent reply other threads:[~2002-05-02 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 21:26 Raidstop /dev/md0 won't work Scott Walter
2002-05-02 21:52 ` Derek Vadala [this message]
2002-05-03 5:00 ` 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=Pine.GSO.4.21.0205021450480.18460-100000@gecko.roadtoad.net \
--to=derek@cynicism.com \
--cc=linux-raid@vger.kernel.org \
--cc=walter@cognigencorp.com \
/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).