public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] /home doesn't umount on shutdown
Date: Tue, 15 Jan 2013 11:57:21 +0200	[thread overview]
Message-ID: <20130115115721.16ea5ca0@khamul.example.com> (raw)

On the rare occasion when I reboot or shut this laptop down, it
continually and consistently gets stuck on one of the final steps, to
umount /home

The process never proceeds beyond that point (as /home is always
fsck'ed on next startup). I can't see any logs as syslog has already
been shut down at this point, and it happens whether I shutdown as root
from the console or by using the KDE widget.

/home here is on LVM

I could probably debug this easily enough if I could determine how the
shutdown sequence is ordered, or get a verbose output. But sadly, my fu
for such stuff has run out.

Anyone got pointers on where to start poking around?

[I'm not looking for solutions, I'm unlikely to get those right off the
bat, just looking for pointers atm]



-- 
Alan McKinnon
alan.mckinnon@gmail.com



             reply	other threads:[~2013-01-15  9:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15  9:57 Alan McKinnon [this message]
2013-01-15 11:09 ` [gentoo-user] /home doesn't umount on shutdown Neil Bothwick
2013-01-15 12:58   ` Alan McKinnon
2013-01-15 14:47     ` Pandu Poluan
2013-01-15 15:06       ` Alan McKinnon
2013-01-15 15:13         ` Volker Armin Hemmann
2013-01-15 22:37     ` [gentoo-user] " Remy Blank
2013-01-15 22:56       ` Dale
2013-01-15 23:12         ` Remy Blank
2013-01-15 23:23           ` Dale
2013-01-16  0:34       ` Alan McKinnon
2013-01-16  5:16         ` Yohan Pereira
2013-01-16  8:33           ` Alan McKinnon
2013-01-15 12:44 ` [gentoo-user] " Dale
2013-01-15 15:03   ` Alan McKinnon

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=20130115115721.16ea5ca0@khamul.example.com \
    --to=alan.mckinnon@gmail.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