[systemd-bugs] [Bug 87929] RFE: more informative mount report upon failure or issue

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87929

--- Comment #2 from Chris Atkinson <cwa at pipeline.com> ---
I Googled for forum threads matching the error message to see how it behaved in
the wild. As ivo thought, most (but not all) of the cases were mount errors. 

Another issue was people not being able to figure out what unit is actually
having the issue as a result of badly written "Description=" tags. (For this
would it be possible to have the error message explicitly include the unit
name, e.g., "A start job is running for Incredibly Bad Description
(foo.service) (89s / 90s)"?)

See below for a proposed catalog entry:

-- 48b695296b4d42fe8c127c20d01bc9bc
Subject: A @TYPE@ job is running for @UNIT@ (@TIME@ / @LIMIT@)
Defined-By: systemd
Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Something has delayed the start or stop job for a unit with the description 
"@UNIT". You will need to debug that unit to see why. @TIME@ of a total 
timeout of @LIMIT@ have elapsed. If you would like to shorten the timeout 
in future, you can edit the "TimeoutStartSec=" or "TimeoutStopSec" 
properties.

A common situation is the delay in mounting a filesystem's *.device unit, 
which is typically caused by problems in "/etc/fstab".

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150111/662d3d9a/attachment.html>