From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-164574-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 8F998138CD3
for <garchives@archives.gentoo.org>; Thu, 28 May 2015 21:38:28 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 09B60E086E;
Thu, 28 May 2015 21:38:22 +0000 (UTC)
Received: from mail-ig0-f171.google.com (mail-ig0-f171.google.com [209.85.213.171])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id EB3DCE085E
for <gentoo-user@lists.gentoo.org>; Thu, 28 May 2015 21:38:20 +0000 (UTC)
Received: by igbpi8 with SMTP id pi8so792513igb.0
for <gentoo-user@lists.gentoo.org>; Thu, 28 May 2015 14:38:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:content-type;
bh=DusWv2HVe8w2WfXyVjKFX6E+5pgYvnrR30RIy2pfVOc=;
b=0cQvPBo7zK+fKfqlPr2qUUUd7mKyxRKbTGLSFKUKgjsZdskaN/3HLPLIVNj51/T9rO
QRJezw8+zqMW87OcDj1ZY1UcjBggt7cZ2DPmIlTUzUFo/Y2/VtJT7tLwuAxUEGnN0/hb
pL0r4ITuwy3MEqjh4+aDl+PvngXeD0QJoEEktx8nYeB020zaCTBeKFSrky7Nu6jnvj2s
eHo2665xWJmTJkQwwcyCebulHGRB7TnBFd40+RBjz30Gd9CFY22CEwsyIaE8U+aUYWJn
iV29bQEhdfUifIVj/YLO1a6hu6p4Vc6JyzR4rtEkJVc9pRAirL9P/zEurxqQuQ15Har+
KVEg==
X-Received: by 10.50.50.148 with SMTP id c20mr73807igo.0.1432849100371; Thu,
28 May 2015 14:38:20 -0700 (PDT)
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.107.25.9 with HTTP; Thu, 28 May 2015 14:37:59 -0700 (PDT)
In-Reply-To: <2981.1432840260@ccs.covici.com>
References: <28995.1432789799@ccs.covici.com> <CADPrc813fwP23rSKzH4SZBREbSQyip3nMHxU6MVGAdX0_xtWZA@mail.gmail.com>
<30995.1432793754@ccs.covici.com> <5566BFF9.7040004@xunil.at>
<1823.1432798791@ccs.covici.com> <5566CA9F.5040608@xunil.at>
<5450.1432801814@ccs.covici.com> <CADPrc8090ymubwU7_V-yOg8Zq2X=sR+pqGxo3n2Hj0w7WOXxcg@mail.gmail.com>
<2981.1432840260@ccs.covici.com>
From: =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw6lz?= <caneko@gmail.com>
Date: Thu, 28 May 2015 16:37:59 -0500
Message-ID: <CADPrc814DhcAWzYBD7f65Qyi8pEt9-gOBPW-OB4d4EK5XYhCNQ@mail.gmail.com>
Subject: Re: [gentoo-user] problems debugging a systemd problem
To: gentoo-user@lists.gentoo.org
Content-Type: multipart/alternative; boundary=047d7bd764bea5090205172b2d7f
X-Archives-Salt: 9eb77b56-74f7-47d0-8f08-dc0f996768d2
X-Archives-Hash: 9155421db170052ccfd81cf14de5023a
--047d7bd764bea5090205172b2d7f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On Thu, May 28, 2015 at 2:11 PM, <covici@ccs.covici.com> wrote:
>
> > Also, as Rich said, if you wait it's possible that systemd (and/or
dracut)
> > will drop you into a rescue shell anyway. Unfortunately, thanks to very
> > slow hardware in the wild, the timeout has been increased to three
minutes,
> > and I believe those are *per hardware unit*. So if you have five disks,
in
> > theory it could take fifteen minutes to get you to a rescue shell.
>
> Thanks much. Does the rescue target try to mount all the disks? Also,
> I would still like to get in touch with the dracut devs -- although I
> may never make that particular mistake again, but maybe other things
> will happen.
As I said in my previous mail: emergency mounts the root filesystem
read-only; rescue mounts all the filesystems read/write. If dracut cannot
mount the root filesystem, it *WILL* drop you to a shell, but it will take
some time while all the timeouts expire. This could be *several* minutes
depending on hardware.
The dracut mailing list is in [1].
Regards.
[1] http://vger.kernel.org/vger-lists.html#initramfs
--
Canek Pel=C3=A1ez Vald=C3=A9s
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Aut=C3=B3noma de M=C3=A9xico
--047d7bd764bea5090205172b2d7f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">On Thu, May 28, 2015 at 2:11 PM, <<a href=3D"mailto:cov=
ici@ccs.covici.com">covici@ccs.covici.com</a>> wrote:<br>><br>> &g=
t; Also, as Rich said, if you wait it's possible that systemd (and/or d=
racut)<br>> > will drop you into a rescue shell anyway. Unfortunately=
, thanks to very<br>> > slow hardware in the wild, the timeout has be=
en increased to three minutes,<br>> > and I believe those are *per ha=
rdware unit*. So if you have five disks, in<br>> > theory it could ta=
ke fifteen minutes to get you to a rescue shell.<br>><br>> Thanks muc=
h.=C2=A0 Does the rescue target try to mount all the disks?=C2=A0 Also,<br>=
> I would still like to get in touch with the dracut devs -- although I<=
br>> may never make that particular mistake again, but maybe other thing=
s<br>> will happen.<br><br>As I said in my previous mail: emergency moun=
ts the root filesystem read-only; rescue mounts all the filesystems read/wr=
ite. If dracut cannot mount the root filesystem, it *WILL* drop you to a sh=
ell, but it will take some time while all the timeouts expire. This could b=
e *several* minutes depending on hardware.<div><br></div><div>The dracut ma=
iling list is in [1].</div><div><br></div><div>Regards.</div><div><br></div=
><div>[1] <a href=3D"http://vger.kernel.org/vger-lists.html#initramfs">http=
://vger.kernel.org/vger-lists.html#initramfs</a><br>--<br>Canek Pel=C3=A1ez=
Vald=C3=A9s<br>Profesor de asignatura, Facultad de Ciencias<br>Universidad=
Nacional Aut=C3=B3noma de M=C3=A9xico</div></div>
--047d7bd764bea5090205172b2d7f--