public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 217604] Kernel metadata repair facility is not available, but kernel has XFS_ONLINE_REPAIR=y
Date: Wed, 28 Jun 2023 21:58:40 +0000	[thread overview]
Message-ID: <bug-217604-201763-eLoFWuNm3U@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217604-201763@https.bugzilla.kernel.org/>

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

--- Comment #1 from Dave Chinner (david@fromorbit.com) ---
On Wed, Jun 28, 2023 at 08:50:43AM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=217604
> 
>             Bug ID: 217604
>            Summary: Kernel metadata repair facility is not available, but
>                     kernel has CONFIG_XFS_ONLINE_REPAIR=y
>            Product: File System
>            Version: 2.5
>           Hardware: All
>                 OS: Linux
>             Status: NEW
>           Severity: normal
>           Priority: P3
>          Component: XFS
>           Assignee: filesystem_xfs@kernel-bugs.kernel.org
>           Reporter: j.fikar@gmail.com
>         Regression: No
> 
> Hi,
> 
> I'm trying the new xfs_scrub and I get this error:
> 
> $ sudo xfs_scrub /mnt/xfs
> EXPERIMENTAL xfs_scrub program in use! Use at your own risk!
> Error: /mnt/xfs: Kernel metadata repair facility is not available.  Use -n to
> scrub.
> Info: /mnt/xfs: Scrub aborted after phase 1.
> /mnt/xfs: operational errors found: 1

We haven't merged all the online repair code yet so it is not yet
available to use. Please close the bug and monitor the upstream XFS
list to find out when the repair code is fully merged and enabled
at runtime.

FWIW, it is far better to send a message to the mailing list
(linux-xfs@vger.kernel.org) to find out what the status of something
is than it is to raise a bug just to ask a question about support...

-Dave.

-- 
You may reply to this email to add a comment.

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

  parent reply	other threads:[~2023-06-28 21:58 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 ` bugzilla-daemon [this message]
2023-06-29  7:10 ` [Bug 217604] Kernel metadata repair facility is not available, but kernel has XFS_ONLINE_REPAIR=y bugzilla-daemon
2023-06-29 14:55   ` Darrick J. Wong
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=bug-217604-201763-eLoFWuNm3U@https.bugzilla.kernel.org/ \
    --to=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