From: "Darrick J. Wong" <djwong@kernel.org>
To: John Zakrzewski <jozakrzewski@microsoft.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Question about fsck for ext4
Date: Tue, 29 Apr 2025 07:46:15 -0700 [thread overview]
Message-ID: <20250429144615.GE25655@frogsfrogsfrogs> (raw)
In-Reply-To: <DS1PR21MB4166208B2E5F4D23F547E349DF802@DS1PR21MB4166.namprd21.prod.outlook.com>
On Tue, Apr 29, 2025 at 01:25:35PM +0000, John Zakrzewski wrote:
> Hi! We are using the k8 utils opensource
> project(https://github.com/kubernetes/utils) and looking for your
> thoughts on an issue where fsck is being run on every remount and if
> this is necessary for journaling filesystems. Eric Sandeen's comments
> here(https://github.com/kubernetes/utils/pull/132#issuecomment-605492335)
> indicate it is not but wanted to verify with you that his statements
> apply to ext4 as well. Ultimately I am looking for reassurance to
> relax the need for fsck on mounts for ext4. I look forward to hearing
> your thoughts and please don't hesitate to ask clarifying questions.
> Thank you!
Running fsck on any journalled filesystem shouldn't be necessary if
they've stopped the practice of snapshotting unfrozen filesystems.
But these days, maybe you /want/ to run fsck in dryrun mode to detect
maliciously corrupt filesystem images before mounting them?
--D
> John Zakrzewski
> Software Engineer
> Azure Core
> jozakrzewski@microsoft.com
>
next prev parent reply other threads:[~2025-04-29 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 13:25 Question about fsck for ext4 John Zakrzewski
2025-04-29 14:46 ` Darrick J. Wong [this message]
2025-04-29 16:31 ` Theodore Ts'o
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=20250429144615.GE25655@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=jozakrzewski@microsoft.com \
--cc=linux-ext4@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