linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] fsck.f2fs output on screen during start-up
Date: Wed, 3 Jun 2020 09:33:06 -0700	[thread overview]
Message-ID: <20200603163306.GA85814@google.com> (raw)
In-Reply-To: <92704294-45ae-7c3a-8cd5-e6f2352f2c53@molgen.mpg.de>

On 06/03, Paul Menzel wrote:
> Dear F2FS folks,
> 
> 
> With Debian Sid/unstable using a F2FS formatted Samsung SSD 850 PRO 512GB as
> root partition, it looks like systemd always run a file system check and
> fsck.f2fs always prints something to the screen (frame buffer), saying
> something with *Fix corruption*.
> 
>     Info: Fix the reported corruption.
> 
> Unfortunately, I am unable to find the message in the systemd journal or
> Linux log (`dmesg`).
> 
> Do you know, what fsck.f2fs is doing differently from the other file system
> check variants?

Well, that's the fsck message, given "-a" option, saying we'll scan the disk,
only if we find a flag raised by in-kernel f2fs during the previous runtime.

Thanks,


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2020-06-03 16:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 16:09 [f2fs-dev] fsck.f2fs output on screen during start-up Paul Menzel
2020-06-03 16:33 ` Jaegeuk Kim [this message]

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=20200603163306.GA85814@google.com \
    --to=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=pmenzel@molgen.mpg.de \
    /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).