linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 220669] Drive issues cause system and coredump and reboot
Date: Thu, 16 Oct 2025 11:10:04 +0000	[thread overview]
Message-ID: <bug-220669-201763-4Lh4Vsj7JT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220669-201763@https.bugzilla.kernel.org/>

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

--- Comment #5 from Brendan Shephard (bshephar@bne-home.net) ---
(In reply to Dave Chinner from comment #2)
> On Thu, Oct 16, 2025 at 12:10:43AM +0000, bugzilla-daemon@kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=220669
> > 
> >             Bug ID: 220669
> >            Summary: Drive issues cause system and coredump and reboot
> >            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: bshephar@bne-home.net
> >         Regression: No
> > 
> > We have a number of drives across our clusters that don't present as
> failing,
> > but seem to have read errors that cause the system to coredump and reboot.
> > Failing drives is obviously not the fault of XFS, but my expectation would
> be
> > that it doesn't completely cause the system to hang and need to reboot.
> 
> Fixed upstream a couple of months back by commit ae668cd567a6 ("xfs:
> do not propagate ENODATA disk errors into xattr code"). You'll need
> to raise a distro bug (Rocky Linux) to get them to back port it for
> you.
> 
> Please close this bz.
> 
> -Dave.

Legend! Thanks for the pointer to the commit. I really appreciate you taking a
look so quickly!

All the best

-- 
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:[~2025-10-16 11:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16  0:10 [Bug 220669] New: Drive issues cause system and coredump and reboot bugzilla-daemon
2025-10-16  0:19 ` [Bug 220669] " bugzilla-daemon
2025-10-16  4:38 ` [Bug 220669] New: " Dave Chinner
2025-10-16  4:38 ` [Bug 220669] " bugzilla-daemon
2025-10-16  8:05 ` bugzilla-daemon
2025-10-16  8:09 ` bugzilla-daemon
2025-10-16 11:10 ` bugzilla-daemon [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=bug-220669-201763-4Lh4Vsj7JT@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;
as well as URLs for NNTP newsgroup(s).