From: Lars Ehrhardt <0104@ng.h42.de>
To: linux-raid@vger.kernel.org
Subject: mdadm --manage --run stops a running array
Date: Wed, 07 Jan 2004 15:26:09 +0100 [thread overview]
Message-ID: <3FFC1701.1000705@ng.h42.de> (raw)
Hi,
I was creating a documentation about a local raid setup and typed
"mdadm --manage --run /dev/md1"
This was on a running array and the command returned:
mdadm: failed to run array "/dev/md1": Device or ressource busy.
I thought, alright, this makes sense /dev/md1 is already started and
mounted as /, so running it again does not work.
Unfortunately I was not able to do anything useful after that, since all
shell commands, like ls failed. Investigating this a bit on a
testmachine I found out that the raid array was shut-down and marked as
clean due to this run command. So, what happened was that the / fs was
still mounted but the raid-device was not running anymore and thus I
could not do anything useful with the system.
I've tested this on two different machines, running kernel 2.4.23 with
the grsecurity patch.
Is this a bug or expected? In my opinion the run command should not stop
an already running (and mounted) array.
Kind regards
Lars
reply other threads:[~2004-01-07 14:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3FFC1701.1000705@ng.h42.de \
--to=0104@ng.h42.de \
--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).