From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] /home doesn't umount on shutdown
Date: Tue, 15 Jan 2013 06:44:11 -0600 [thread overview]
Message-ID: <50F54F1B.2010606@gmail.com> (raw)
In-Reply-To: <20130115115721.16ea5ca0@khamul.example.com>
Alan McKinnon wrote:
> 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]
>
>
>
I would do a 'rc single' then use lsof for /home to see what if anything
is still going on. I think with openrc, when you go to single user it
unmounts about everything, tho this could have changed since it has been
a while since I went to single user. Oh, I have had issues going from
single user back to default mode. It just doesn't work right. So, be
ready to reboot if needed.
I ran into a weird issue one time a long time ago. It turned out it was
the order I had them in fstab. I think I had /usr/portage above /usr so
as it went down the file, it was trying to mount /usr/portage then
trying to mount /usr. I thought it rather odd, maybe a bug even, but
changing the order made it work. Do you maybe have something in a odd
order in fstab?
Well, it's early and I am still half asleep. Hope that helps. Going
back to bed. To wet to go hunting this morning, sleeting too. Brrrrrr!
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
next prev parent reply other threads:[~2013-01-15 12:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 9:57 [gentoo-user] /home doesn't umount on shutdown Alan McKinnon
2013-01-15 11:09 ` 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 ` Dale [this message]
2013-01-15 15:03 ` [gentoo-user] " 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=50F54F1B.2010606@gmail.com \
--to=rdalek1967@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