public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: covici@ccs.covici.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] problems debugging a systemd problem
Date: Thu, 28 May 2015 19:57:41 -0400	[thread overview]
Message-ID: <21085.1432857461@ccs.covici.com> (raw)
In-Reply-To: <CADPrc814DhcAWzYBD7f65Qyi8pEt9-gOBPW-OB4d4EK5XYhCNQ@mail.gmail.com>

Canek Peláez Valdés <caneko@gmail.com> wrote:

> 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.

OK, thanks much.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com


  reply	other threads:[~2015-05-28 23:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28  5:09 [gentoo-user] problems debugging a systemd problem covici
2015-05-28  5:38 ` Canek Peláez Valdés
2015-05-28  6:15   ` covici
2015-05-28  7:12     ` Stefan G. Weichinger
2015-05-28  7:39       ` covici
2015-05-28  7:58         ` Stefan G. Weichinger
2015-05-28  8:30           ` covici
2015-05-28  8:59             ` Stefan G. Weichinger
2015-05-28 11:46               ` covici
2015-05-28 15:57             ` Canek Peláez Valdés
2015-05-28 17:46               ` Rich Freeman
2015-05-28 18:11                 ` Canek Peláez Valdés
2015-05-28 18:36                   ` Rich Freeman
2015-05-28 21:32                     ` Canek Peláez Valdés
2015-05-28 21:55                       ` covici
2015-05-28 22:25                         ` Rich Freeman
2015-05-28 22:27                         ` Canek Peláez Valdés
2015-05-28 22:23                       ` Rich Freeman
2015-05-28 22:34                         ` Canek Peláez Valdés
2015-05-28 19:11               ` covici
2015-05-28 21:37                 ` Canek Peláez Valdés
2015-05-28 23:57                   ` covici [this message]
2015-06-01 13:55                     ` Stefan G. Weichinger
2015-06-01 14:04                       ` covici
2015-05-28 11:23     ` Rich Freeman
2015-05-28 14:12       ` covici

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=21085.1432857461@ccs.covici.com \
    --to=covici@ccs.covici.com \
    --cc=gentoo-user@lists.gentoo.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