You are not logged in.

#1 2011-11-09 00:46:30

oboedad55
Member
From: Baku
Registered: 2011-04-05
Posts: 392

[SOLVED] shutdown log

Hi, I've googled the heck out of this with no love. I'm getting a message on shutdwon that goes by so fast I can't read it. I've checked all logs with no results. Is there some way to log the shutdown?

Last edited by oboedad55 (2011-11-09 17:33:17)


Registered Linux user #436067

Offline

#2 2011-11-09 01:01:14

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [SOLVED] shutdown log

Maybe http://mailman.archlinux.org/pipermail/ … 22344.html will help.

Edit: He meant /etc/rc.shutdown, not rc.conf.

Last edited by karol (2011-11-09 01:02:32)

Offline

#3 2011-11-09 02:34:23

oboedad55
Member
From: Baku
Registered: 2011-04-05
Posts: 392

Re: [SOLVED] shutdown log

Great, thanks Karol. I just remembered, the message says something about /sbin/blkid. /dev/sda.... then "failed".


Registered Linux user #436067

Offline

#4 2011-11-09 03:46:09

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,111
Website

Re: [SOLVED] shutdown log

I can't find the bug report, so the tl;dr version is: you have a swap partition which emits a CHANGED uevent when its disabled during shutdown. The event is handled by udev which immediately gets told to quit after receiving the event, and in turn, shuts down its children. One of these children is running blkid on the swap device that it received the CHANGED uevent for. The result is that you see the 'terminated' message for the udev child that's running blkid. In the end, it's harmless. Maybe some day I'll get around to implementing something like a --files-only flag for swapoff.

Offline

#5 2011-11-09 05:54:43

oboedad55
Member
From: Baku
Registered: 2011-04-05
Posts: 392

Re: [SOLVED] shutdown log

falconindy wrote:

I can't find the bug report, so the tl;dr version is: you have a swap partition which emits a CHANGED uevent when its disabled during shutdown. The event is handled by udev which immediately gets told to quit after receiving the event, and in turn, shuts down its children. One of these children is running blkid on the swap device that it received the CHANGED uevent for. The result is that you see the 'terminated' message for the udev child that's running blkid. In the end, it's harmless. Maybe some day I'll get around to implementing something like a --files-only flag for swapoff.

Ah OK, falconindy, thanks for the reply. That makes sense. It wasn't causing a problem, but I like to have everything working properly.


Registered Linux user #436067

Offline

Board footer

Powered by FluxBB