From: Martin Wilck <mwilck@suse.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>,
Luke Pyzowski <Luke@sunrisefutures.com>,
"'systemd-devel@lists.freedesktop.org'"
<systemd-devel@lists.freedesktop.org>,
linux-raid@vger.kernel.org
Subject: Re: Errorneous detection of degraded array
Date: Fri, 27 Jan 2017 09:25:02 +0100 [thread overview]
Message-ID: <1485505502.4903.6.camel@suse.com> (raw)
In-Reply-To: <b842c2ce-7d32-a392-e9d9-9f330fa6a7cf@gmail.com>
> 26.01.2017 21:02, Luke Pyzowski пишет:
> > Hello,
> > I have a large RAID6 device with 24 local drives on CentOS7.3.
> > Randomly (around 50% of the time) systemd will unmount my RAID
> > device thinking it is degraded after the mdadm-last-resort@.timer
> > expires, however the device is working normally by all accounts,
> > and I can immediately mount it manually upon boot completion. In
> > the logs below /share is the RAID device. I can increase the timer
> > in /usr/lib/systemd/system/mdadm-last-resort@.timer from 30 to 60
> > seconds, but this problem can randomly still occur.
It seems to me that you rather need to decrease the timeout value, or
(more reasonable) increase x-systemd.device-timeout for the /share
mount point.
Unfortunately your log excerpt contains to time stamps but I suppose
you're facing a race where the device times out before the "last
resort" timer starts it (and before the last devices appear).
Martin
--
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
next prev parent reply other threads:[~2017-01-27 8:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <96A26C8C6786C341B83BC4F2BC5419E4795DE9A6@SRF-EXCH1.corp.sunrisefutures.com>
2017-01-27 7:12 ` [systemd-devel] Errorneous detection of degraded array Andrei Borzenkov
2017-01-27 8:25 ` Martin Wilck [this message]
2017-01-27 19:44 ` Luke Pyzowski
2017-01-28 17:34 ` [systemd-devel] " Andrei Borzenkov
2017-01-30 22:41 ` Luke Pyzowski
2017-01-30 1:53 ` NeilBrown
2017-01-30 3:40 ` Andrei Borzenkov
2017-01-30 6:36 ` NeilBrown
2017-01-30 7:29 ` Andrei Borzenkov
2017-01-30 22:19 ` [systemd-devel] " NeilBrown
2017-01-31 20:17 ` Andrei Borzenkov
2017-02-08 4:10 ` NeilBrown
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=1485505502.4903.6.camel@suse.com \
--to=mwilck@suse.com \
--cc=Luke@sunrisefutures.com \
--cc=arvidjaar@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=systemd-devel@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).