From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lennart Poettering Subject: Re: systemd kills mdmon if it was started manually by user Date: Fri, 7 Jan 2011 01:40:24 +0100 Message-ID: <20110107004024.GE21627@tango.0pointer.de> References: <201012041012.23757.trapni@gentoo.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: systemd-devel-bounces+gcssd-systemd-devel=m.gmane.org@lists.freedesktop.org Errors-To: systemd-devel-bounces+gcssd-systemd-devel=m.gmane.org@lists.freedesktop.org To: Andrey Borzenkov Cc: linux-raid@vger.kernel.org, systemd-devel@lists.freedesktop.org List-Id: linux-raid.ids On Sat, 04.12.10 15:08, Andrey Borzenkov (arvidjaar@gmail.com) wrote: > >> It is then killed by systemd during shutdown as part of user session. > >> It results in dirty array on next boot. > >> > >> Is there any magic that allows daemon to be exempted from killing? > > > > While your raid should absolutely not be corrupted on next reboot > > when mdmon receives a SIGTERM, > > This won't be corrupted but it will initiate rebuilt. I have reports > that such rebuild may take hours, costing performance and loss of > redundancy. Well, eventually we need to be able to kill mdmon. Otherwise we might not be able to remount the root dir r/o. How exactly is mdmon supposed to behave on shutdown? Lennart -- Lennart Poettering - Red Hat, Inc.