From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: NeilBrown <neilb@suse.com>
Cc: Mikulas Patocka <mpatocka@redhat.com>,
Shaohua Li <shli@kernel.org>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] md: don't use flush_signals in userspace processes
Date: Fri, 9 Jun 2017 00:27:28 -0300 [thread overview]
Message-ID: <20170609032728.GA25899@khazad-dum.debian.net> (raw)
In-Reply-To: <87shja9b7s.fsf@notabene.neil.brown.name>
On Fri, 09 Jun 2017, NeilBrown wrote:
> Or maybe it could be discarded - the md_check_recovery() thing.
> The idea was that if you alt-sysrq-K to kill all processes, md arrays
> would go into immediate-safe-mode where the metadata is marked clean
> immediately after writes finish, rather than waiting a few seconds. The
> chance of having a clean array after shutdown is hopefully improved.
>
> I've never actually used this though, and I doubt many people know about
> it. And bitmaps make it fairly pointless.
Hmm, I have, although I had no idea this was why my arrays were getting
far less frazzled than expected... It is really useful behavior, now
that I know it can do that.
If you can teach SysRq+S, and especially SysRq+U, to force all arrays
into safe-mode *after* they carried their current meanings
(sync/umount), that would be more useful though, and it would help a lot
of people to avoid dirty arrays without them even knowing why...
--
Henrique Holschuh
prev parent reply other threads:[~2017-06-09 3:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 23:05 [PATCH] md: don't use flush_signals in userspace processes Mikulas Patocka
2017-06-08 6:59 ` NeilBrown
2017-06-08 17:15 ` Shaohua Li
2017-06-08 20:51 ` Mikulas Patocka
2017-06-08 21:24 ` NeilBrown
2017-06-08 22:58 ` Shaohua Li
2017-06-09 1:49 ` NeilBrown
2017-06-08 22:52 ` Mikulas Patocka
2017-06-09 1:55 ` NeilBrown
2017-06-09 3:27 ` Henrique de Moraes Holschuh [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=20170609032728.GA25899@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mpatocka@redhat.com \
--cc=neilb@suse.com \
--cc=peterz@infradead.org \
--cc=shli@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