linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: linux-ext4@vger.kernel.org, nux-kernel@vger.kernel.org
Subject: [bugreport] Ext4 automatically checked at each boot
Date: Wed, 1 Jan 2020 15:58:25 +0500	[thread overview]
Message-ID: <CABXGCsODr3tMpQxJ_nhWQQg5WGakFt4Yu5B8ev6ErOkc+zv9kA@mail.gmail.com> (raw)

Hi folks.

Strange things happen with my ext4 lately:
- At each boot, the file system is checked.
- When I launch fsck manually it didn't found any issue.
- But tune2fs report that last checked and mount time is Sun Dec 15,
but this is incorrect.

I don’t know where to look further so I ask here for help.


Here is tune2fs report: https://pastebin.com/PZPbAuHS

# cat /etc/fstab

#
# /etc/fstab
# Created by anaconda on Mon Sep  9 19:36:53 2019
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
UUID=b3e2e027-c39d-4266-871f-22d313ac419b /                       ext4
   defaults        1 1
UUID=E8A2-F389          /boot/efi               vfat
umask=0077,shortname=winnt 0 2
UUID=bf3e9504-8000-42a1-adb4-226658ec7a5d /home                   ext4
   defaults        1 2
UUID=f47f69e1-61f8-4024-960a-b3981d3b1d02 none                    swap
   defaults        0 0


--
Best Regards,
Mike Gavrilov.

             reply	other threads:[~2020-01-01 10:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-01 10:58 Mikhail Gavrilov [this message]
2020-01-01 12:30 ` [bugreport] Ext4 automatically checked at each boot Mikhail Gavrilov
2020-01-01 14:17 ` Theodore Y. Ts'o
2020-01-01 23:19   ` Mikhail Gavrilov
2020-01-02  8:08     ` [bugreport] "hwclock -w" reset time instead of setting the right time Mikhail Gavrilov
2020-01-02 11:08       ` Karel Zak
2020-01-02 11:55         ` Mikhail Gavrilov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABXGCsODr3tMpQxJ_nhWQQg5WGakFt4Yu5B8ev6ErOkc+zv9kA@mail.gmail.com \
    --to=mikhail.v.gavrilov@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=nux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).