mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Czigola Gabor <czigola@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: root MD array is still in use upon shutdown possible fix
Date: Mon, 9 Oct 2006 10:40:13 +1000	[thread overview]
Message-ID: <17705.39533.439604.522302@cse.unsw.edu.au> (raw)
In-Reply-To: message from Czigola Gabor on Friday October 6

On Friday October 6, czigola@elte.hu wrote:
> Hi!
> 
> When my root filesystem is on an MD (RAID5) array, I can't cleanly shut 
> down (trying to change the array ro, even when nothing else than the 
> kernel threads and init and one bash are running, and the root fs is ro 
> remounted), because I've got "md: md0 still in use" kernel messages. 
> Usually it doesn't cause any problems, but it possibly could leave the 
> array in an inconsistent state (resync required after reboot).

When your machine shuts down, all md arrays are automatically switched to
read-only *after* the root filesystem has been unmounted.  You should
get a message 
    md: stopping all md devices.

if you get e.g.
    md: md0 still in use.
*after* that message then there might be a problem.  Otherwise
everything should be fine.

That being said, it is possible that your patch is OK.  I've been
meaning to review the rules for switching an array to read-only for
ages, but it never got to the top of the todo list.  e.g. do you want
to be able to switch an array to read-only when a filesystem is
mounted read-write off it.  If you don't, how do you check?  If you
do, what about in-flight write requests?  Do you need to wait for them
to complete? How? It isn't as straight forward as one might like.

NeilBrown

  reply	other threads:[~2006-10-09  8:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06 18:26 Czigola Gabor
2006-10-09  0:40 ` Neil Brown [this message]
2006-10-16  1:56   ` Czigola Gabor

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=17705.39533.439604.522302@cse.unsw.edu.au \
    --to=neilb@suse.de \
    --cc=czigola@elte.hu \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®