Bug#785463: mount: remounting root file system with lazytime broken
Hello Jörg-Volker Peetz. Thanks for helping out testing my initial fears that I broke something in util-linux is not the case. The bug has been confirmed to be on the Linux side in the ext4 driver, see http://thread.gmane.org/gmane.comp.file-systems.ext4/48676/focus=48678 I've reassigned your bug report to src:linux already. Since you're using a custom built kernel you'll need to wait for upstream to produce a patch for linux you can apply, build and test. Hopefully this will be resolved in Debian soon in an upcoming stable kernel update. No patch is yet available as far as I know. Hopefully soon. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785463: mount: remounting root file system with lazytime broken
Hello Andreas, Andreas Henriksson wrote on 05/17/2015 21:39: Hello Jörg-Volker Peetz. Thanks for your bug report. On Sat, May 16, 2015 at 06:44:53PM +0200, Jörg-Volker Peetz wrote: Package: mount, util-linux Version: 2.26.2-2 Severity: normal Dear Maintainer, since version 2.26 the remounting of the root file system with lazytime/nolazytime seems to be broken. The command # mount -o remount,lazytime / has no effect if lazytime is not set. Could you please check if commenting out the following row in debian/rules and rebuilding the package makes any difference for this issue? CONFOPTS += --enable-libmount-force-mountinfo Quick hints for rebuilding the package: cd /tmp apt-get source util-linux cd util-linux # edit debian/rules to comment or delete the row mentioned above. apt-get build-dep util-linux dpkg-buildpackage -uc -us dpkg -i ../libmount_*.deb ../mount_*.deb Maybe that change is completely unrelated to your issue, but would be appreciated if you could help me out with checking if so. snip Following your instructions, I re-built the util-linux package. I installed the packages mount, libmount1, util-linux, and libfdisk1. Before being able to do that, I had to update the sysvinit related packages. Still, I'm not able to manipulate the lazytime mount option. The mount state is $ grep -E '(root|sda)' /proc/mounts /dev/root / ext4 rw,lazytime,relatime,nobarrier,errors=remount-ro 0 0 /dev/sda2 /home ext4 rw,lazytime,relatime,nobarrier,errors=remount-ro 0 0 As root I commanded # strace -o /tmp/st mount -o remount,nolazytime / # grep ^mount /tmp/st mount(/dev/sda1, /, 0xf00780, MS_MGC_VAL|MS_REMOUNT, nobarrier,errors=remount-ro) = 0 But nothing changed in /proc/mounts. -- Regards, Jörg. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785463: mount: remounting root file system with lazytime broken
Hello Andreas, Andreas Henriksson wrote on 05/17/2015 21:39: Hello Jörg-Volker Peetz. Thanks for your bug report. On Sat, May 16, 2015 at 06:44:53PM +0200, Jörg-Volker Peetz wrote: Package: mount, util-linux Version: 2.26.2-2 Severity: normal Dear Maintainer, since version 2.26 the remounting of the root file system with lazytime/nolazytime seems to be broken. The command # mount -o remount,lazytime / has no effect if lazytime is not set. Could you please check if commenting out the following row in debian/rules and rebuilding the package makes any difference for this issue? CONFOPTS += --enable-libmount-force-mountinfo Quick hints for rebuilding the package: cd /tmp apt-get source util-linux cd util-linux # edit debian/rules to comment or delete the row mentioned above. apt-get build-dep util-linux dpkg-buildpackage -uc -us dpkg -i ../libmount_*.deb ../mount_*.deb Thanks for the instructions. Before going further in this direction some more informations: In order to get the lazytime mount option set for the root file system, the /etc/fstab entry was not enough, I had to use the kernel parameter rootflags=lazytime also. I use a self compiled stable kernel 4.0.3 without initramfs. Meanwhile I've downgraded to util-linux version 2.25.2-5, where this bug is not present. There's some discussion going on upstream, about where the bug is really located, see, e.g., http://article.gmane.org/gmane.comp.file-systems.ext4/48663 and http://thread.gmane.org/gmane.comp.file-systems.ext4/48676 Maybe that change is completely unrelated to your issue, but would be appreciated if you could help me out with checking if so. I'll check it as soon as possible. Also I see a warning like findfs: unable to resolve UUID=... (don't remember the exact message) during the boot process. Please check your system logs and provide full details about this. I should have sent this in another bug report as wishlist. This message appears also with util-linux 2.25.2-5. The message appears only on the boot screen and the uuid is the one of the root file system. It reads findfs: unable to resolve 'UUID=1f7c8ee0-...' where I substituted '...' for the rest of the uuid. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785463: mount: remounting root file system with lazytime broken
Hello Jörg-Volker Peetz. Thanks for your bug report. On Sat, May 16, 2015 at 06:44:53PM +0200, Jörg-Volker Peetz wrote: Package: mount, util-linux Version: 2.26.2-2 Severity: normal Dear Maintainer, since version 2.26 the remounting of the root file system with lazytime/nolazytime seems to be broken. The command # mount -o remount,lazytime / has no effect if lazytime is not set. Could you please check if commenting out the following row in debian/rules and rebuilding the package makes any difference for this issue? CONFOPTS += --enable-libmount-force-mountinfo Quick hints for rebuilding the package: cd /tmp apt-get source util-linux cd util-linux # edit debian/rules to comment or delete the row mentioned above. apt-get build-dep util-linux dpkg-buildpackage -uc -us dpkg -i ../libmount_*.deb ../mount_*.deb Maybe that change is completely unrelated to your issue, but would be appreciated if you could help me out with checking if so. Also I see a warning like findfs: unable to resolve UUID=... (don't remember the exact message) during the boot process. Please check your system logs and provide full details about this. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785463: mount: remounting root file system with lazytime broken
Package: mount, util-linux Version: 2.26.2-2 Severity: normal Dear Maintainer, since version 2.26 the remounting of the root file system with lazytime/nolazytime seems to be broken. The command # mount -o remount,lazytime / has no effect if lazytime is not set. Also I see a warning like findfs: unable to resolve UUID=... (don't remember the exact message) during the boot process. -- Regards, jvp. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.3 (SMP w/2 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages mount depends on: ii libblkid1 2.26.2-2 ii libc6 2.19-18 ii libmount1 2.26.2-2 ii libselinux12.3-2 ii libsmartcols1 2.26.2-2 mount recommends no packages. Versions of packages mount suggests: pn nfs-common none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
