Your message dated Fri, 14 Oct 2022 02:26:20 +0200 with message-id <y0isrmfhbufjc...@thunder.hadrons.org> and subject line Re: Bug#923423: dpkg: Hangs for 19 mins installing texlive-fonts-extra has caused the Debian Bug report #923423, regarding dpkg: package install can be very slow with some disks due to too frequent fsync to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 923423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: texlive-fonts-extra Version: 2018.20190227-1 Severity: serious Installation of texlive-fonts-extra 2018.20190227-1 hangs. Here's px information: # px 5553 /usr/bin/dpkg --status-fd 80 --no-triggers --unpack --auto-deconfigure --recursive /tmp/apt-dpkg-install-mos7uq kernel(0) root init(1) root lightdm(915) root lightdm(1525) root zsh(1547) vinc17 fvwm2(1629) vinc17 sh(1745) vinc17 xterm(1746) vinc17 zsh(1750) vinc17 su(1839) root bash(1841) root aptitude(2012) root ----------------------> dpkg(5553) root 17m01s ago dpkg was started, at 2019-02-28T00:48:45+01:00. 1.5% has been its average CPU usage since then, or 15s/17m01s Other processes started close to dpkg(5553): [kworker/0:1-events](5351) was started 2m57s before dpkg(5553) [kworker/u17:0-kcryptd](5540) was started 1.0s before dpkg(5553) [kworker/4:2](5771) was started 2m19s after dpkg(5553) [kworker/u16:1-events_unbound](5928) was started 4m21s after dpkg(5553) [kworker/5:2-mm_percpu_wq](6068) was started 5m06s after dpkg(5553) Users logged in when dpkg(5553) started: vinc17 from 155.133.131.76 vinc17 from :0 2019-02-28T01:05:46.585799: Now invoking lsof, this can take over a minute on a big system... 2019-02-28T01:05:47.098503: lsof done, proceeding. File descriptors: stdin : [CHR] /dev/pts/16 stdout: [CHR] /dev/pts/16 stderr: [CHR] /dev/pts/16 Network connections: Inter Process Communication: aptitude(2012): [FIFO] pipe For a list of all open files, do "sudo lsof -p 5553", or "sudo watch lsof -p 5553" for a live view. -- Package-specific info: IMPORTANT INFORMATION: We will only consider bug reports concerning the packaging of TeX Live as relevant. If you have problems with combination of packages in a LaTeX document, please consult your local TeX User Group, the comp.text.tex user group, the author of the original .sty file, or any other help resource. In particular, bugs that are related to up-upstream, i.e., neither Debian nor TeX Live (upstream), but the original package authors, will be closed immediately. *** The Debian TeX Team is *not* a LaTeX Help Desk *** If you report an error when running one of the TeX-related binaries (latex, pdftex, metafont,...), or if the bug is related to bad or wrong output, please include a MINIMAL example input file that produces the error in your report. Please run your example with (pdf)latex -recorder ... (or any other program that supports -recorder) and send us the generated file with the extension .fls, it lists all the files loaded during the run and can easily explain problems induced by outdated files in your home directory. Don't forget to also include minimal examples of other files that are needed, e.g. bibtex databases. Often it also helps to include the logfile. Please, never send included pictures! If your example file isn't short or produces more than one page of output (except when multiple pages are needed to show the problem), you can probably minimize it further. Instructions on how to do that can be found at http://www.minimalbeispiel.de/mini-en.html (english) or http://www.minimalbeispiel.de/mini.html (german) ################################## minimal input file ################################## other files ###################################### List of ls-R files -rw-r--r-- 1 root root 2880 2019-02-27 03:14:07 /var/lib/texmf/ls-R lrwxrwxrwx 1 root root 29 2018-09-02 14:32:33 /usr/share/texmf/ls-R -> /var/lib/texmf/ls-R-TEXMFMAIN lrwxrwxrwx 1 root root 31 2019-02-27 01:08:59 /usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST lrwxrwxrwx 1 root root 31 2019-02-27 01:08:59 /usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST ###################################### Config files -rw-r--r-- 1 root root 475 2018-09-02 20:20:53 /etc/texmf/web2c/texmf.cnf lrwxrwxrwx 1 root root 33 2019-02-27 01:08:59 /usr/share/texmf/web2c/fmtutil.cnf -> /var/lib/texmf/fmtutil.cnf-DEBIAN lrwxrwxrwx 1 root root 32 2019-02-27 01:08:59 /usr/share/texmf/web2c/updmap.cfg -> /var/lib/texmf/updmap.cfg-DEBIAN -rw-r--r-- 1 root root 5089 2019-02-27 03:13:40 /var/lib/texmf/tex/generic/config/language.dat ###################################### Files in /etc/texmf/web2c/ total 8 -rw-r--r-- 1 root root 283 2014-10-21 02:46:09 mktex.cnf -rw-r--r-- 1 root root 475 2018-09-02 20:20:53 texmf.cnf ###################################### md5sums of texmf.d ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-3-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages texlive-fonts-extra depends on: it tex-common 6.10 ii texlive-base 2018.20190207-1 Versions of packages texlive-fonts-extra recommends: ii fonts-adf-accanthis 0.20110505-3 ii fonts-adf-berenis 0.20110505-3 ii fonts-adf-gillius 0.20110505-3 ii fonts-adf-universalis 0.20110505-3 ii fonts-cabin 1.5-2 ii fonts-comfortaa 3.001-2 ii fonts-croscore 20181227-1 ii fonts-crosextra-caladea 20130214-2 ii fonts-crosextra-carlito 20130920-1 ii fonts-dejavu-core 2.37-1 ii fonts-dejavu-extra 2.37-1 ii fonts-ebgaramond 0.016-1 ii fonts-ebgaramond-extra 0.016-1 ii fonts-font-awesome 4.7.0~dfsg-3 ii fonts-freefont-otf 20120503-9 ii fonts-freefont-ttf 20120503-9 ii fonts-gfs-artemisia 1.1-5 ii fonts-gfs-complutum 1.1-6 ii fonts-gfs-didot 1.1-6 ii fonts-gfs-neohellenic 1.1-6 ii fonts-gfs-olga 1.1-5 ii fonts-gfs-solomos 1.1-5 ii fonts-go 0~20170330-1 ii fonts-junicode 1.001-2 ii fonts-lato 2.0-2 ii fonts-linuxlibertine 5.3.0-4 ii fonts-lobstertwo 2.0-2 ii fonts-noto-hinted 20181227-1 ii fonts-noto-mono 20181227-1 ii fonts-oflb-asana-math 000.907-6 ii fonts-open-sans 1.11-1 pn fonts-roboto-hinted <none> ii fonts-roboto-unhinted 2:0~20170802-2 ii fonts-sil-gentium 20081126:1.03-2 ii fonts-sil-gentium-basic 1.102-1 ii fonts-sil-gentiumplus 5.000-2 ii fonts-sil-gentiumplus-compact 5.000-2 ii fonts-stix 1.1.1-4 iu texlive-fonts-extra-links 2018.20190227-1 pn texlive-latex-extra <none> Versions of packages texlive-fonts-extra suggests: ii cm-super 0.3.4-13 iu texlive-fonts-extra-doc 2018.20190227-1 Versions of packages tex-common depends on: ii dpkg 1.19.5 ii ucf 3.0038+nmu1 Versions of packages tex-common suggests: ii debhelper 12.1.1 Versions of packages texlive-fonts-extra is related to: it tex-common 6.10 ii texlive-binaries 2018.20181218.49446-1 -- debconf information: tex-common/check_texmf_wrong: tex-common/check_texmf_missing:
--- End Message ---
--- Begin Message ---Hi! On Tue, 2019-04-09 at 11:34:08 +0200, Vincent Lefevre wrote: > I'm not sure. This may just be a slow disk after all, and in practice > (I mean except benchmarking), the problem seems specific to dpkg. > I assume that programs normally don't do a fsync at every fraction > of microsecond! I don't know what dpkg is trying to achieve with such > a frequency of fsync, but this doesn't seem to make sense to me. You > had said "which has been the solution to earlier problems with ext4", > but the real solution would be to fix ext4 (does "earlier" mean this > has eventually been fixed?). All these fsync()s you see in rapid succession are used as a synchronization points, way after the data has been requested to be synced to disk asynchronously via sync_file_range(). What this is trying to achieve is durability, so that dpkg can know the data is on the disk, so that it can mark the package as installed. This is explained on the dpkg FAQ: <https://wiki.debian.org/Teams/Dpkg/FAQ#Q:_Why_is_dpkg_so_slow_when_using_new_filesystems_such_as_btrfs_or_ext4.3F> > > It seems to me either hardware, filesystem or kernel related as > > mentioned before. > > I've seen https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785020 > "fsync is slow on later kernels with ext4 filesystms" but the comments > in this bug page and 4.19.28-1 kernel logs show that this has been > fixed. > > FYI, I get very similar timings on the same machine, but on /boot, > which is: > > /dev/sda1 on /boot type ext2 > (rw,relatime,block_validity,barrier,user_xattr,acl,stripe=4) > > The fact that the main, ext4 partition is encrypted but not this > one makes another difference, but the timings are similar, so that > this doesn't seem to be related to the FS system itself and appears > to be at a lower level. > > Note also that my machine is a laptop, and I couldn't do a comparison > with other laptops, just in case. > > > Could you reassign where you think it would be more appropriate? > > I think that this should still be regarded as a dpkg bug, based on > my first paragraph above (the fsync's occur much too often in dpkg > compared to other programs, and this doesn't seem to be useful). Most programs do not seem concerned about making sure the data is stored safely on disk, I'm afraid. In any case, I don't think there's anything else for dpkg to do here. Please see the FAQ entry. I'm thus closing this now. Thanks, Guillem
--- End Message ---
