mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Czigola Gabor <czigola@elte.hu>
To: Neil Brown <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: root MD array is still in use upon shutdown possible fix
Date: Mon, 16 Oct 2006 03:56:06 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0610160344100.8154@kamorka> (raw)
In-Reply-To: <17705.39533.439604.522302@cse.unsw.edu.au>

Thank you for your answer!

On Mon, 9 Oct 2006, Neil Brown wrote:

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

Yes, I've got exactly that, and rarely after such a reboot the array 
started to resync.

> 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

I realised afterwrds, that this patch makes it possible to stop an array 
even it has a rw mounted filesystem on it. But I can easily remember not 
to switch the array to ro before umounting (remouning ro) the 
filesystem(s) on it, in return the array stops surely sync-d.

Of course, this isn't a solution for the kernel. But wouldn't it be 
possible to get the required information from the mount tables of the 
kernel? About pending write request to the md device does the subsystem 
already know.

-- 
Czigola, Gabor

      reply	other threads:[~2006-10-16  1:56 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
2006-10-16  1:56   ` Czigola Gabor [this message]

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.LNX.4.64.0610160344100.8154@kamorka \
    --to=czigola@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    /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®