From: "Darrick J. Wong" <djwong@kernel.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: cem@kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 4/4] xfs: enable online fsck by default in Kconfig
Date: Wed, 3 Sep 2025 12:38:51 -0700 [thread overview]
Message-ID: <20250903193851.GK8096@frogsfrogsfrogs> (raw)
In-Reply-To: <0b88c35a-9616-4ad9-9dec-978902f0e901@suse.cz>
On Wed, Sep 03, 2025 at 08:07:29PM +0200, Vlastimil Babka wrote:
> On 9/3/25 17:00, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> >
> > Online fsck has been a part of upstream for over a year now without any
> > serious problems. Turn it on by default in time for the 2025 LTS
> > kernel.
> >
> > Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
> > ---
> > fs/xfs/Kconfig | 8 ++------
> > 1 file changed, 2 insertions(+), 6 deletions(-)
> >
> >
> > diff --git a/fs/xfs/Kconfig b/fs/xfs/Kconfig
> > index ecebd3ebab1342..dc55bbf295208d 100644
> > --- a/fs/xfs/Kconfig
> > +++ b/fs/xfs/Kconfig
> > @@ -137,7 +137,7 @@ config XFS_BTREE_IN_MEM
> >
> > config XFS_ONLINE_SCRUB
> > bool "XFS online metadata check support"
> > - default n
> > + default y
> > depends on XFS_FS
> > depends on TMPFS && SHMEM
> > select XFS_LIVE_HOOKS
> > @@ -150,8 +150,6 @@ config XFS_ONLINE_SCRUB
> > advantage here is to look for problems proactively so that
> > they can be dealt with in a controlled manner.
> >
> > - This feature is considered EXPERIMENTAL. Use with caution!
> > -
> > See the xfs_scrub man page in section 8 for additional information.
> >
> > If unsure, say N.
>
> Should it still say that with default y?
I suppose not. :D
--D
> > @@ -175,7 +173,7 @@ config XFS_ONLINE_SCRUB_STATS
> >
> > config XFS_ONLINE_REPAIR
> > bool "XFS online metadata repair support"
> > - default n
> > + default y
> > depends on XFS_FS && XFS_ONLINE_SCRUB
> > select XFS_BTREE_IN_MEM
> > help
> > @@ -186,8 +184,6 @@ config XFS_ONLINE_REPAIR
> > formatted with secondary metadata, such as reverse mappings and inode
> > parent pointers.
> >
> > - This feature is considered EXPERIMENTAL. Use with caution!
> > -
> > See the xfs_scrub man page in section 8 for additional information.
> >
> > If unsure, say N.
>
> Ditto
>
next prev parent reply other threads:[~2025-09-03 19:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 14:59 [PATCHSET] xfs: kconfig and feature changes for 2025 LTS Darrick J. Wong
2025-09-03 14:59 ` [PATCH 1/4] xfs: disable deprecated features by default in Kconfig Darrick J. Wong
2025-09-05 8:30 ` Carlos Maiolino
2025-09-03 15:00 ` [PATCH 2/4] xfs: remove deprecated mount options Darrick J. Wong
2025-09-05 8:35 ` Carlos Maiolino
2025-09-05 15:25 ` Darrick J. Wong
2025-09-03 15:00 ` [PATCH 3/4] xfs: remove deprecated sysctl knobs Darrick J. Wong
2025-09-05 8:36 ` Carlos Maiolino
2025-09-03 15:00 ` [PATCH 4/4] xfs: enable online fsck by default in Kconfig Darrick J. Wong
2025-09-03 18:07 ` Vlastimil Babka
2025-09-03 19:38 ` Darrick J. Wong [this message]
2025-09-04 2:43 ` [PATCH v1.1 " Darrick J. Wong
2025-09-05 8:39 ` Carlos Maiolino
-- strict thread matches above, loose matches on Subject: below --
2025-09-05 15:55 [PATCHSET 6.18 v2 2/2] xfs: kconfig and feature changes for 2025 LTS Darrick J. Wong
2025-09-05 15:58 ` [PATCH 4/4] xfs: enable online fsck by default in Kconfig Darrick J. Wong
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=20250903193851.GK8096@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=vbabka@suse.cz \
/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