lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Thu, 02 Jan 2020 15:16:25 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 206061] Poor NVME SSD support, EXT4 re-mounted

https://bugzilla.kernel.org/show_bug.cgi?id=206061

Theodore Tso (tytso@....edu) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tytso@....edu

--- Comment #1 from Theodore Tso (tytso@....edu) ---
These kernel messages (modulo the timestamps) are normal.   The root file
system is mounted read-only, and after the file system is checked, the file
system is mounted read-write.

What is not supposed to be happening is the file system getting checked after
every boot.   I would need to look at the fsck logs to be sure, but the most
likely cause is that your motherboard's real time clock is not correctly set,
or the battery for the real time clock is dead.

Normally, when the kernel is booted, it sets the system clock from the
motherboard's real-time clock, and then the file system is mounted, it is
checked, and then it is remounted read-write.   After that, the network is set
up, and the time gets set from an internet time server.  The motherboard's real
time clock should be set after the time is set from the internet time server
(to correct it from clock drift), and most init scripts will also set the
hardware clock from the system clock at shutdown.  And then the real-time clock
will be maintained even while the power is off using the battery on the
motherboard.  (It's normally a watch battery, such as a CR2032.)

To work around something going wrong with the above, please try adding to
/etc/e2fsck.conf --- or creating /etc/e2fsck.conf if it does not exist --- the
following lines

[options]
    broken_system_clock = true

More information about this can be found in the e2fsck.conf man page.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

Powered by blists - more mailing lists