Skip to contentSkip to conversation

New: Poor NVME SSD support, EXT4 re-mounted

Bug 206061 [email protected] 1 participant 2 messages Jan 2, 2020

lore
Share & tools
lore

[email protected]

author
#0 lore raw

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

            Bug ID: 206061
           Summary: Poor NVME SSD support, EXT4 re-mounted
           Product: File System
           Version: 2.5
    Kernel Version: 4.18, 5.3
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: low
          Priority: P1
         Component: ext4
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

Good time of day. After every time I turned on my computer on Xubuntu 18.04, I saw that my disk's file system was being checked. In dmesg, I saw the following:

[    1.422390] EXT4-fs (nvme0n1p3): mounted filesystem with ordered data mode.
Opts: (null)
[    3.522543] EXT4-fs (nvme0n1p3): re-mounted. Opts: (null)

. On the Internet, I found out that this is an old SSD NVME problem that can't be fixed for 2 years. Why are you not going to support new hardware and the kernel displays such messages after each run? This problem affects many users.

Signature · 2 lines
You are receiving this mail because:
You are watching the assignee of the bug.
author
#1 lore raw

[Bug 206061] Poor NVME SSD support, EXT4 re-mounted

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

Theodore Tso ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #1 from Theodore Tso ([email protected]) ---
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.

Signature · 2 lines
You are receiving this mail because:
You are watching the assignee of the bug.