<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - systemd-fsck@dev-mapper-home.service takes an abnormally time of 30s to complete during boot"
href="https://bugs.freedesktop.org/show_bug.cgi?id=89873">89873</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>systemd-fsck@dev-mapper-home.service takes an abnormally time of 30s to complete during boot
</td>
</tr>
<tr>
<th>Product</th>
<td>systemd
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>zebul666@hotmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre><a href="mailto:systemd-fsck@dev-mapper-home.service">systemd-fsck@dev-mapper-home.service</a> takes 30s to complete during boot whereas
fs are clean. this also seems to happen for other fs, but randomly (?)
Using systemd 219 on Ubuntu 15.04 (beta 2), I noticed an abnormally long boot
sequence (given the use of a SSD) with wait on "Checking filesystem on disk
..."
This happens on every boot. The same setup with upstart/systemd and ubuntu
14.10 showed no such problem.
It appears that:
$ systemd-analyze blame|head -3
32.241s <a href="mailto:systemd-fsck@dev-mapper-home.service">systemd-fsck@dev-mapper-home.service</a>
8.137s plymouth-quit-wait.service
7.691s NetworkManager-wait-online.service
$ systemctl status <a href="mailto:systemd-fsck@dev-mapper-home.service">systemd-fsck@dev-mapper-home.service</a>
● <a href="mailto:systemd-fsck@dev-mapper-home.service">systemd-fsck@dev-mapper-home.service</a> - File System Check on /dev/mapper/home
Loaded: loaded (/lib/systemd/system/systemd-fsck@.service; static; vendor
preset: enabled)
Active: active (exited) since mer. 2015-04-01 22:45:58 CEST; 2h 45min ago
Docs: man:systemd-fsck@.service(8)
Main PID: 821 (code=exited, status=0/SUCCESS)
avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck progress
to fsckd: Broken pipe
avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck progress
to fsckd: Broken pipe
avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck progress
to fsckd: Broken pipe
avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck progress
to fsckd: Broken pipe
avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck progress
to fsckd: Broken pipe
avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck progress
to fsckd: Broken pipe
avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck progress
to fsckd: Broken pipe
avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck progress
to fsckd: Broken pipe
avril 01 22:45:58 callisto systemd-fsck[821]: /dev/mapper/home :
169002/13148160 fichiers (0.8% non contigus), 36631520/52566272 blocs
avril 01 22:45:58 callisto systemd[1]: Started File System Check on
/dev/mapper/home.
I can check from ext4 metadata header that no fsck is actually run. fsck
returns immediatly. the fs has already been check and is clean.
The setup is as follow on an Inspiron 15 3525.
/dev/sda is a SSD with root on /dev/sda4 and /dev/sda5 being a bcache caching
device for /dev/sdb5 bcache backing LUKS home partition. sdb is a hdd in an hdd
caddy in dvd drive bay.
home == LUKS: bcache0: sda5+sdb5
using fsck.mode=skip avoids that 30s wait, but that is not really wanted.
/etc/crypttab:
home /dev/bcache0 /root/.xxxxxxxxx-6xxx-4xxx-axxx-xxxxxxxxxx.bin luks
cryptswap /dev/disk/by-partuuid/xxxxxxxx-0xxx-4xxx-bxxx-xxxxxxxxx
/dev/urandom swap,cipher=aes-cbc-essiv:sha256,size=256</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>