public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Filipe Manana <fdmanana@kernel.org>
Cc: Boris Burkov <boris@bur.io>, Josef Bacik <josef@toxicpanda.com>,
	QuWenruo <wqu@suse.com>, Qu Wenruo <quwenruo.btrfs@gmx.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	Chris Murphy <lists@colorremedies.com>,
	Zygo Blaxell <ce3g8jdj@umail.furryterror.org>,
	Roman Mamedov <rm@romanrm.net>
Subject: Re: BTRFS error (device dm-4): failed to run delayed ref for logical 350223581184 num_bytes 16384 type 176 action 1 ref_mod 1: -117 (kernel 6.11.2)
Date: Thu, 27 Feb 2025 11:57:14 -0800	[thread overview]
Message-ID: <20250227195714.GF11500@merlins.org> (raw)
In-Reply-To: <CAL3q7H4n0Akdk22ecLvdj87mP6iET1F9uUFB1Uzm+t+hCE_DHw@mail.gmail.com>

On Thu, Feb 27, 2025 at 05:41:29PM +0000, Filipe Manana wrote:
> > I will merge the patch and report back since I seem to be able to
> > reproduce easily.
> 
> The patch was backported to 6.11.3, you're on 6.11.2... can't you
> update the kernel to 6.11.11 (the last 6.11 stable kernel)?

I totally can, I didn't know what the bug was, or which kernels it was
fixed in, and don't have time to upgrade to every point release unless
there is a need, which there is in this case.
Will upgrade now, thanks much for the guidance, much appreciated.

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
 
Home page: http://marc.merlins.org/  

      reply	other threads:[~2025-02-27 19:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 17:07 BTRFS error (device dm-4): failed to run delayed ref for logical 350223581184 num_bytes 16384 type 176 action 1 ref_mod 1: -117 (kernel 6.11.2) Marc MERLIN
2025-02-06 17:34 ` Marc MERLIN
2025-02-25  7:32 ` Marc MERLIN
2025-02-25  8:07   ` Qu Wenruo
2025-02-25  8:29     ` Marc MERLIN
2025-02-25  8:46       ` Qu Wenruo
2025-02-25  9:18         ` Marc MERLIN
2025-02-25  9:22           ` Qu Wenruo
2025-02-27 14:11             ` Marc MERLIN
2025-02-27 15:05               ` Marc MERLIN
2025-02-28 13:10               ` Marc MERLIN
2025-02-25  9:25           ` Roman Mamedov
2025-02-27 17:02 ` Boris Burkov
2025-02-27 17:21   ` Boris Burkov
2025-02-27 17:33     ` Marc MERLIN
2025-02-27 17:41       ` Filipe Manana
2025-02-27 19:57         ` Marc MERLIN [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=20250227195714.GF11500@merlins.org \
    --to=marc@merlins.org \
    --cc=boris@bur.io \
    --cc=ce3g8jdj@umail.furryterror.org \
    --cc=fdmanana@kernel.org \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=quwenruo.btrfs@gmx.com \
    --cc=rm@romanrm.net \
    --cc=wqu@suse.com \
    /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