Bug 847701 - timeouts on shutdown stopping LUKS device units
Summary: timeouts on shutdown stopping LUKS device units
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 17
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-13 09:59 UTC by htd
Modified: 2012-09-14 09:28 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 857406 (view as bug list)
Environment:
Last Closed: 2012-09-14 09:28:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Log on shutdown (532.10 KB, image/jpeg)
2012-08-13 09:59 UTC, htd
no flags Details
Fstab (1.04 KB, text/plain)
2012-08-16 10:00 UTC, htd
no flags Details
Crypttab (270 bytes, text/plain)
2012-08-16 10:01 UTC, htd
no flags Details

Description htd 2012-08-13 09:59:12 UTC
Created attachment 603944 [details]
Log on shutdown

Description of problem:
Shutting down takes several minutes.

Version-Release number of selected component (if applicable):
systemd-sysv-44-17.fc17.x86_64
systemd-44-17.fc17.x86_64

How reproducible:
Problem occurs on shutting down from XFCE graphical env., in ca. 75% of all cases.

Steps to Reproduce:
1. shutdown
2.
3.
  
Actual results:
Shutdown is delayed 2-3 minutes with several "time outs". See attached picture.

Expected results:
Machine shuts down in acceptable time.

Additional info:
See attached picture for what shows up on the screen. First it hangs ~ 2 min after the first two lines, and ca. 2 minutes again where the lines on the pictures end.

Comment 1 htd 2012-08-13 17:55:47 UTC
Switching to runlevel 3 and shutting down via "shutdown -h now" works without any delay, as expected.

Comment 2 htd 2012-08-16 08:59:52 UTC
Btw, here's an identical report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679114

Tried "TimeoutSec=3" without any success.

Comment 3 Michal Schmidt 2012-08-16 09:39:47 UTC
Please attach /etc/fstab and /etc/crypttab.

Comment 4 htd 2012-08-16 10:00:08 UTC
Created attachment 604870 [details]
Fstab

Comment 5 htd 2012-08-16 10:01:49 UTC
Created attachment 604873 [details]
Crypttab

Comment 6 htd 2012-08-18 10:30:52 UTC
After reading a lot, trying a lot and installing a fresh fully encryted F17 on another machine, I give up. And I have to take back that booting into runlevel 3 and "shutdown -h now" helps; it doesn't. With a 2:3 chance, my systems hang on shutdown for several minutes, as shown on the attached picture. I tried all I could come over and to, without success. 

Since this is a "business" machine I'm using for my mastergrade studies, it's simply unacceptable to have to wait this long when shutting down.I'm travelling a lot, and to leave the harddisk unencrypted is no option either, especially because this problem was not present in F15/F16.

So if somebody has a fix or a workaround I'd be very thankful!

In the meantime, I'm forced to install another distribution (Arch) on my main machine and get things copied over, before the weekend is gone, to get rid of this. I'll keep one of the machines untouched, in case I can help to explore/fix this bug (which I'm more than willing to).

Comment 7 htd 2012-09-01 17:46:45 UTC
Now, after nearly 3 weeks since I reported this bug without a single useful reply, there's only one Fedora machine left, all the others run Arch now, which hasn't this annoying behaviour. So dear bug-maintainer/asignee, whoever you are - you can close this one. Since Arch works as expected, I do not care any longer. The last Fedora machine will be re-installed later this week.

Comment 8 Lennart Poettering 2012-09-14 09:27:47 UTC
OK, closing.

If you still want to help, we'd appreciate getting the output of dmesg of shutdown as explained here:

http://freedesktop.org/wiki/Software/systemd/Debugging#Diagnosing_Shutdown_Problems

If you attach that output, please reopen the bug.


Note You need to log in before you can comment on or make changes to this bug.