touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #67457
[Bug 1439445] Re: systemd-fsck laps 30s on boot for /dev/mapper/home
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1439445/+attachment/4363682/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1439445
Title:
systemd-fsck laps 30s on boot for /dev/mapper/home
Status in systemd package in Ubuntu:
New
Bug description:
Using 15.04 beta 2 witht the following setup:
/dev/sda is a SSD (crucial mx100) in main SATA port of Inspiron 15 3521
/dev/sdb is a hdd in an hdd caddy in sata original dvd drive bay
root is /dev/sda4 on SSD
/dev/sda5 is a caching bcache partition (on SSD) for the /dev/sdb5 bcache backing LUKS home partition
/etc/crypttab:
home /dev/bcache0 /root/.xxxxxxxxx-64bd-44ca-a46e-xxxxxxxxxx.bin luks
For an unknown reason, during boot, systemd-fsck laps 30s for doing a fsck on /dev/mapper/home.
But the fsck is not really run, it should return immediatly
$ systemd-analyze blame|head -3
32.241s systemd-fsck@dev-mapper-home.service
8.137s plymouth-quit-wait.service
7.691s NetworkManager-wait-online.service
$ systemctl status systemd-fsck@dev-mapper-home.service
● systemd-fsck@dev-mapper-home.service - 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.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-4ubuntu10
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 2 01:24:15 2015
InstallationDate: Installed on 2015-04-01 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
MachineType: Dell Inc. Inspiron 3521
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed root=UUID=cxxxxx-xxxx-xxxx-xxxxx-xxxxxxxxxxx ro quiet splash
SourcePackage: systemd
UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/25/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: XXXXXX
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A12
dmi.modalias: dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rnXXXXX:rvrA02:cvnDellInc.:ct8:cvrA12:
dmi.product.name: Inspiron 3521
dmi.product.version: A12
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1439445/+subscriptions
References