On 29-11-15 01:28, Michael Biebl wrote:
Am 29.11.2015 um 00:12 schrieb Manuel Bilderbeek:
How can I help?
Describe your setup in as much detail as possible. LVM, RAID, fstab etc.
No RAID, no LVM. I've got a HDD and an SSD. I'm now booting from the SSD.
$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdg1 during installation
UUID=8efc387d-cdc0-496d-8f3c-03cc7f4ac8a5 / ext4
errors=remount-ro,noatime 0 1
# swap was on /dev/sdg5 during installation
UUID=0a3f3e1b-1141-4033-b619-ec2f6d62b452 none swap sw
0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/sr1 /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/sda1 /media/olddisk1 ext4 ro,noatime 0 2
/dev/sda6 /media/olddisk6 ext4 rw,noatime 0 2
/media/olddisk6/manuel/Music /home/manuel/Music none
defaults,bind,rw 0 0
/media/olddisk6/manuel/Pictures /home/manuel/Pictures none
defaults,bind,rw 0 0
/media/olddisk6/manuel/photos /home/manuel/photos none
defaults,bind,rw 0 0
/media/olddisk6/manuel/Documents /home/manuel/Documents none
defaults,bind,rw 0 0
/media/olddisk6/manuel/Videos /home/manuel/Videos none
defaults,bind,rw 0 0
/media/olddisk6/manuel/msx-soft /home/manuel/msx-soft none
defaults,bind,rw 0 0
/media/olddisk6/manuel/docs /home/manuel/docs none
defaults,bind,rw 0 0
As you can see I'm bind-mounting some dirs from my HDD (which is
olddisk6) into my homedir.
Can you reproduce the issue with arbitrary mounts?
Um, not sure, how do I test that exactly?
Can you reproduce the issue with a minimal setup? On a different system?
I don't have another system to test with. I don't know how to go to a
'minimal setup'.
Do you have any hints how we can reproduce it?
I didn't do anything special for it, as I said, just dist-upgrading
daily. But this was one of the first times the fsck was due for that
disk after the reinstall on the SSD, I guess.
Does the problem go away if you use "systemctl mask
systemd-fsckd.service systemd-fsckd.socket"
I'll report about that later. But first tell me: what does this do and
how can I undo it if necessary?
Does journalctl -u systemd-fsckd.service produce anything interesting?
$ sudo journalctl -u systemd-fsckd.service
-- Logs begin at zo 2015-11-29 11:11:00 CET, end at zo 2015-11-29
14:27:42 CET. --
nov 29 11:11:00 sonata systemd[1]: Started File System Check Daemon to
report status.
Can you boot with systemd.debug-shell on the kernel command line, and
then switch to tty9 while the fsck is running and attach strace to the
fsckd and fsck process?
I'll try that next reboot.
--
Grtjs, Manuel
PS: MSX FOR EVER! (Questions? http://faq.msxnet.org/ )
PPS: Visit my homepage at http://manuel.msxnet.org/
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
