https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c zhang jiajun changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |sbrabec@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c3 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbrabec@suse.com --- Comment #3 from Stanislav Brabec 2014-03-25 17:02:50 CET --- What is your /etc/fstab? I guess that it is a deliberate default behavior for file systems with journa, because large disc or arrays can require hours to complete fsck. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c5 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |fcrozat@suse.com AssignedTo|bnc-team-screening@forge.pr |sbrabec@suse.com |ovo.novell.com | --- Comment #5 from Stanislav Brabec 2014-03-25 17:20:13 CET --- I just consulted it. The current way to disable checks by default is handled by YaST installation. It resets check time interval and maximal mount count by default. If you set your file systems differently, it should check. It is either problem of fsck, or systemd does not set command line arguments to run the check. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c7 --- Comment #7 from Martin Schröder 2014-03-26 12:12:33 CET --- (In reply to comment #6)

and the output of:

for i in `systemctl list-units | grep fsck | cut -d " " -f1`; do systemctl status $i; done

systemd-fsck@dev-datengrab-backup.service - File System Check on /dev/datengrab/backup Loaded: loaded (/usr/lib/systemd/system/systemd-fsck@.service; static) Active: active (exited) since Di 2014-03-25 10:35:12 CET; 1 day 1h ago Docs: man:systemd-fsck@.service(8) Main PID: 626 (code=exited, status=0/SUCCESS) systemd-fsck@dev-datengrab-space.service - File System Check on /dev/datengrab/space Loaded: loaded (/usr/lib/systemd/system/systemd-fsck@.service; static) Active: active (exited) since Di 2014-03-25 10:35:12 CET; 1 day 1h ago Docs: man:systemd-fsck@.service(8) Main PID: 623 (code=exited, status=0/SUCCESS) systemd-fsck@dev-disk-by\x2did-ata\x2dINTEL_SSDSA2M080G2GN_CVPO017402JP080JGN\x2dpart1.service - File System Check on /dev/disk/by-id/ata-INTEL_SSDSA2M080G2GN_CVPO017402JP080JGN-part1 Loaded: loaded (/usr/lib/systemd/system/systemd-fsck@.service; static) Active: active (exited) since Di 2014-03-25 10:35:08 CET; 1 day 1h ago Docs: man:systemd-fsck@.service(8) Main PID: 556 (code=exited, status=0/SUCCESS) systemd-fsck@dev-system-home.service - File System Check on /dev/system/home Loaded: loaded (/usr/lib/systemd/system/systemd-fsck@.service; static) Active: active (exited) since Di 2014-03-25 10:35:09 CET; 1 day 1h ago Docs: man:systemd-fsck@.service(8) Main PID: 586 (code=exited, status=0/SUCCESS) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c9 --- Comment #9 from Martin Schröder 2014-03-26 12:14:58 CET --- Created an attachment (id=583754) --> (http://bugzilla.novell.com/attachment.cgi?id=583754) sudo journalctl -xb >/tmp/journalctl-xb.txt -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c10 Martin Schröder changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #580532|0 |1 is obsolete| | --- Comment #10 from Martin Schröder 2014-03-26 12:16:09 CET --- Created an attachment (id=583755) --> (http://bugzilla.novell.com/attachment.cgi?id=583755) /etc/fstab -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c12 --- Comment #12 from Thomas Blume 2014-03-26 11:52:01 UTC --- Can you please run it manually, e.g.: /usr/lib/systemd/systemd-fsck /dev/sda1 and afterwards check via tune2fs wheter the checktime was updated? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c14 --- Comment #14 from Dr. Werner Fink 2014-03-26 12:08:20 UTC --- Last checked: Sat Sep 21 13:32:49 2013 Check interval: 15552000 (6 months) Next check after: Thu Mar 20 12:32:49 2014 doesn't look correct -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c16 Martin Schröder changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|martin@oneiros.de | --- Comment #16 from Martin Schröder 2014-03-26 14:29:34 CET --- (In reply to comment #15)

fsck.ext4 without the option -f doesn't update the checktime either. Can you please reboot the machine with the kernel comand line parameter:

fsck.mode=force

and check again?

Works. tune2fs 1.42.9 (28-Dec-2013) Filesystem volume name: <none> Last mounted on: /boot Filesystem UUID: 4ac0e637-e02f-4667-9194-42ccd47e27c9 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 66264 Block count: 264192 Reserved block count: 13209 Free blocks: 194367 Free inodes: 65922 First block: 1 Block size: 1024 Fragment size: 1024 Reserved GDT blocks: 256 Blocks per group: 8192 Fragments per group: 8192 Inodes per group: 2008 Inode blocks per group: 251 Flex block group size: 16 Filesystem created: Wed Nov 24 12:27:30 2010 Last mount time: Wed Mar 26 14:14:54 2014 Last write time: Wed Mar 26 14:14:54 2014 Mount count: 1 Maximum mount count: 36 Last checked: Wed Mar 26 14:14:52 2014 Check interval: 15552000 (6 months) Next check after: Mon Sep 22 15:14:52 2014 Lifetime writes: 4462 MB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: ce434223-13e5-48fa-b7c9-b51c6e706d3b Journal backup: inode blocks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c18 Thomas Blume changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mchang@suse.com --- Comment #18 from Thomas Blume 2014-03-26 13:52:28 UTC --- Ok, seems we need to add fsck.mode=force to the /etc/default/grub settings. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c20 --- Comment #20 from Martin Schröder 2014-03-26 14:56:30 CET --- (In reply to comment #19)

IMHO this may cause that on every boot the file systems will be checked .. ?

Yes. All fs will be fsckd always. Please fix the bug instead. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c22 Martin Schröder changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|martin@oneiros.de | --- Comment #22 from Martin Schröder 2014-03-26 15:10:33 CET --- (In reply to comment #21)

(In reply to comment #20)

you may try to set the maximum mount count by using

tune2fs -c 2 /dev/sda1

and test if this cause a file system check on next reboot. Also please show the kernels command line using

Without fsck.mode=force it does not. Time and count "violations" are reported (and apparently an fsck is done, see comment #11 - but not recorded). Or do you want me to test fsck.mode=force? If you look at the bootlog which I attached, you will see fscks for _all_ fs, even those I previously fscked manually.

cat /proc/cmdline

cat /proc/cmdline root=/dev/system/root resume=/dev/system/swap fsck.mode=force vga=0x3e6

also attach /etc/e2fsck.conf

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c24 --- Comment #24 from Thomas Blume 2014-03-26 14:22:16 UTC --- The old file system check in /etc/init.d/boot.local included the -A option of fsck as default. According to the manpage, this seems to be the one we need: -->-- -A Walk through the /etc/fstab file and try to check all filesystems in one run. This option is typically used from the /etc/rc system initialization file, instead of multiple commands for checking a single filesystem. The root filesystem will be checked first unless the -P option is specified (see below). After that, filesystems will be checked in the order specified by the fs_passno (the sixth) field in the /etc/fstab file. Filesystems with a fs_passno value of 0 are skipped and are not checked at all. --<-- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c26 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jack@suse.com, pth@suse.com --- Comment #26 from Dr. Werner Fink 2014-03-26 14:36:36 UTC --- Adding the maintainers of e2fsprogs ... IMHO the e2fsck seems to be broken or some more tricky at least for the journaling ext4 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c28 --- Comment #28 from Martin Schröder 2014-03-28 00:56:16 CET --- (In reply to comment #27)

So there are likely two things at play: 1) e2fsck doesn't do any checking (unless -f is specified) if the system is running on battery (there is defer_check_on_battery=0 option to turn off this feature).

The systems in question are not running on battery.

2) e2fsck doesn't do any time based checks if broken_system_clock option is set to 1. We do set this option in /etc/e2fsck.conf with the justification to not stop booting due to broken clocks. This is the culprit of the problem reported by Stanislav. I'll have a look how to fix this.

Please see comment #11. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c30 --- Comment #30 from Martin Schröder 2014-05-20 14:48:53 CEST --- Just a datapoint from 12.3: After the recent kernel update (to 3.7.10-1.32-desktop) I rebooted the system. mounts exceeding the counts are reported and force fscks (which also reset the count and set the last check time); mounts exceeding the times are only reported. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

sudo tune2fs -l /dev/dm-1 tune2fs 1.42.8 (20-Jun-2013) Filesystem volume name: <none> Last mounted on: /root Filesystem UUID: a7b21580-3d4f-49db-8448-6aff9b9822e7 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c32 --- Comment #32 from Martin Schröder 2014-08-14 12:58:58 CEST --- Sorry, bus it's not fixed. Today I rebooted my server and got this: Aug 14 09:12:59 lucien kernel: EXT4-fs (dm-1): warning: checktime reached, running e2fsck is recommended Aug 14 09:12:59 lucien kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: acl,user_xattr,journal_checksum Aug 14 09:12:59 lucien kernel: EXT4-fs (dm-1): re-mounted. Opts: acl,user_xattr,journal_checksum dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 3276800 Block count: 13107200 Reserved block count: 655360 Free blocks: 10834251 Free inodes: 3146038 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 1020 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Flex block group size: 16 Filesystem created: Thu Jun 9 16:12:24 2011 Last mount time: Thu Aug 14 09:12:56 2014 Last write time: Thu Aug 14 09:12:56 2014 Mount count: 20 Maximum mount count: 23 Last checked: Mon Aug 19 12:39:47 2013 Check interval: 15552000 (6 months) Next check after: Sat Feb 15 11:39:47 2014 Lifetime writes: 8 TB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: 73fa5be8-0cfd-4963-b326-a30f2ed9b316 Journal backup: inode blocks

rpm -qi e2fsprogs Name : e2fsprogs Version : 1.42.8 Release : 2.1.2 Architecture: x86_64 Install Date: Mi 21 Mai 2014 15:19:13 CEST Group : System/Filesystems Size : 2431576 License : GPL-2.0 Signature : RSA/SHA256, Fr 27 Sep 2013 22:04:26 CEST, Key ID b88b2fd43dbdc284 Source RPM : e2fsprogs-1.42.8-2.1.2.src.rpm Build Date : Fr 27 Sep 2013 22:04:06 CEST Build Host : cloud134 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : http://e2fsprogs.sourceforge.net Summary : Utilities for the Second Extended File System Description : Utilities needed to create and maintain ext2 and ext3 file systems under Linux. Included in this package are: chattr, lsattr, mke2fs, mklost+found, tune2fs, e2fsck, resize2fs, and badblocks. Distribution: openSUSE 13.1

So nothing has changed since comment 30. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c34 Jan Kara changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |martin@oneiros.de --- Comment #34 from Jan Kara 2014-08-14 11:34:13 UTC --- Well, the bug is fixed in Factory only and that has 1.42.11. I didn't push the updated package to 13.1. If the bug really bothers you, I can push just the fix for this bug into 13.1... So does it? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c36 --- Comment #36 from Martin Schröder 2014-08-14 14:04:56 CEST --- (In reply to comment #35)

I checked with .11 - it works for non-root filesystems. / is still not fscked.

Btw: My / is on LVM. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c38 --- Comment #38 from Jan Kara 2014-08-14 14:07:55 UTC --- Created an attachment (id=602401) --> (http://bugzilla.novell.com/attachment.cgi?id=602401) [PATCH] Fix last mount time and last write time in preen mode I've added this patch to e2fsprogs in 13.1. Then broken_system_clock in /etc/e2fsck.conf can be set to 0 without the risk that boot will fail due to bad system time and time-based checks are working again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c40 Benjamin Brunner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED CC| |bbrunner@suse.com InfoProvider|maintenance@opensuse.org | --- Comment #40 from Benjamin Brunner 2014-08-25 14:36:13 CEST --- I'm sorry for the late reply. I was out of office for the last 2 weeks. Jan could you open a maintenancerequest with the updated 13.1 package please? Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c43 Matthias Grießmeier changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #43 from Matthias Grießmeier 2014-09-02 07:28:12 UTC --- Update released for openSUSE 13.1 - resolved fixed -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.