public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 204997] New: fsck.xfs prints a vague message "XFS file system" when skipping a boot time check
Date: Wed, 25 Sep 2019 17:51:35 +0000	[thread overview]
Message-ID: <bug-204997-201763@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 204997
           Summary: fsck.xfs prints a vague message "XFS file system" when
                    skipping a boot time check
           Product: File System
           Version: 2.5
    Kernel Version: 5.4
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: low
          Priority: P1
         Component: XFS
          Assignee: filesystem_xfs@kernel-bugs.kernel.org
          Reporter: nf8kh699qb@liamekaens.com
        Regression: No

Created attachment 285173
  --> https://bugzilla.kernel.org/attachment.cgi?id=285173&action=edit
Suggested patch to improve the error message seen on boot.

When an XFS filesystems is configured to be checked on boot via the /etc/fstab,
the /usr/sbin/fsck.xfs is called. It does nothing but print "XFS file system"
which can mislead admins into thinking the filesytem was checked when it has
not been.

This was previously reported via RedHat bug
https://bugzilla.redhat.com/show_bug.cgi?id=1546294 and is a minor issue.

Steps to Reproduce:
1. Change the "0 0" in /etc/fstab for /home to "0 1"
2. Reboot and watch console messages

Actual results:

Observe "Started file system check on /dev/mapper/<name of home LV>"

Observe "systemd-fsck[<PID>]: /sbin/fsck.xfs: XFS file system"

Expected results:

Observe "systemd-fsck[<PID>]: /sbin/fsck.xfs: XFS file system checks always
skipped on boot"

Or some other message to make it clear that the check was 1) skipped and 2)
this was intentional

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

                 reply	other threads:[~2019-09-25 17:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-204997-201763@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-xfs@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