From: NeilBrown <neilb@suse.de>
To: Francis Moreau <francis.moro@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Accesses to not yet running array
Date: Wed, 21 Aug 2013 09:06:34 +1000 [thread overview]
Message-ID: <20130821090634.413491d8@notabene.brown> (raw)
In-Reply-To: <CAC9WiBgjEQxe_uymD6WW3Oj5Bm6aYD-RBD-8m3G40c1y3HUb0Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
On Tue, 20 Aug 2013 16:08:47 +0200 Francis Moreau <francis.moro@gmail.com>
wrote:
> hi,
>
> It looks like a process wait uninterruptibly when it tries to access
> an array which is not running yet.
>
> Furthermore once the process is waiting, I can't start/stop the array anymore.
>
> So I need to reboot my system and be sure next time that any processes
> don't try to access a not yet running array.
>
> Is that expected ?
>
No.
To be able to say more I would need lots more details.
What is the exact state of the array (cat /proc/mdstat ;mdadm -D ...)
Where is the process waiting (cat /proc/PID/stack)
What sort of "access"
How did the array get to the "not running yet" state?
Any kernel messages?
Anything else that might be relevant.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-08-20 23:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 14:08 Accesses to not yet running array Francis Moreau
2013-08-20 23:06 ` NeilBrown [this message]
2013-08-21 13:57 ` Francis Moreau
2013-08-23 10:00 ` Francis Moreau
2013-08-23 19:09 ` Martin Wilck
2013-08-24 12:40 ` Francis Moreau
2013-08-24 12:42 ` Francis Moreau
2013-08-24 18:41 ` Martin Wilck
2013-08-26 4:33 ` NeilBrown
2013-08-27 8:11 ` Francis Moreau
2013-08-26 5:30 ` NeilBrown
2013-08-26 7:30 ` Francis Moreau
2013-08-26 7:53 ` NeilBrown
2013-08-26 8:16 ` Francis Moreau
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=20130821090634.413491d8@notabene.brown \
--to=neilb@suse.de \
--cc=francis.moro@gmail.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