The machine has been stable for a couple of days, and I tested today
that fsck finished OK.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubu
I installed the 229-4ubuntu11 version. If the system is stable till the
weekend, and does not hang/crash/livelock/deadlock/whatever happened
when I tested the ubuntu9 version, I'll twiddle max mount count to force
fsck during the weekend.
--
You received this bug notification because you are a m
I have had 229-4ubuntu10 version now for the packages, and the machine
has not crashed yet (last crash was Friday morning, so 2 days without
crash...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://b
this might be unrelated, but since I tried the xenial-proposed packages, the
computer has crashed about once a day. Usually I don't get any info on syslog,
but I found this on syslog today:
Sep 30 13:32:28 xpc kernel: [19560.717703] INFO: task jbd2/dm-1-8:879 blocked
for more than 120 seconds.
now it worked. the packages I needed:
kex@xpc:~$ sudo dpkg -l | grep 229
ii libpam-systemd:amd64 229-4ubuntu9
amd64system and service manager -
PAM module
ii libsystemd0:amd64
hi,
the packet fails to install:
kex@xpc:~$ LANG=en sudo apt-get install systemd/xenial-proposed
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '229-4ubuntu9' (Ubuntu:16.04/xenial-proposed [amd64]) for
'systemd
Then: running fsck in recovery mode works nice:
root@xpc:~# fsck /dev/mapper/xpcvg-home
fsck – util-linux 2.26.2
e2fsck 1.42.12 (29-Aug-2014)
/dev/mapper/xpcvg-home has been mounted 166 times without being checked, check
forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directo
Public bug reported:
during normal boots, fsck runs fine with small partitions. But I have two big
partitions and systemd seems to abort fsck somewhere between 5 to 10 minutes
from start. This results in the partition being checked again at every boot.
After manual run in recovery mode, eve
8 matches
Mail list logo
