From: "Darrick J. Wong" <djwong@kernel.org>
To: bugzilla-daemon@kernel.org
Cc: linux-xfs@vger.kernel.org
Subject: Re: [Bug 217604] Kernel metadata repair facility is not available, but kernel has XFS_ONLINE_REPAIR=y
Date: Thu, 29 Jun 2023 07:55:35 -0700 [thread overview]
Message-ID: <20230629145535.GC11441@frogsfrogsfrogs> (raw)
In-Reply-To: <bug-217604-201763-INXcwbWsOM@https.bugzilla.kernel.org/>
On Thu, Jun 29, 2023 at 07:10:35AM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=217604
>
> j.fikar@gmail.com changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|NEW |RESOLVED
> Resolution|--- |DOCUMENTED
>
> --- Comment #2 from j.fikar@gmail.com ---
> OK Dave, I'll do that. Maybe the help for XFS_ONLINE_REPAIR can mention that it
> is not yet working, to avoid future confusion.
Both kernel and userspace yell EXPERIMENTAL when you invoke any part of
the online fsck system; I thought that was sufficient...
--D
> Actually, I was reporting another kernel bug (vmalloc error), which was
> probably seen before and currently it is in network drivers (no idea, why it is
> there).
>
> I'm telling you, as it might be XFS related. I see the bug exactly once a day
> and when I look at my cron.daily jobs, it happens during xfs_fsr run.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=217502
>
> --
> You may reply to this email to add a comment.
>
> You are receiving this mail because:
> You are watching the assignee of the bug.
next prev parent reply other threads:[~2023-06-29 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 8:50 [Bug 217604] New: Kernel metadata repair facility is not available, but kernel has CONFIG_XFS_ONLINE_REPAIR=y bugzilla-daemon
2023-06-28 21:58 ` Dave Chinner
2023-06-28 21:58 ` [Bug 217604] Kernel metadata repair facility is not available, but kernel has XFS_ONLINE_REPAIR=y bugzilla-daemon
2023-06-29 7:10 ` bugzilla-daemon
2023-06-29 14:55 ` Darrick J. Wong [this message]
2023-06-29 14:55 ` bugzilla-daemon
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=20230629145535.GC11441@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=bugzilla-daemon@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