All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicholas D Steeves <sten@debian.org>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
	Brett Dikeman <brett.dikeman@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: corrupt leaf, invalid data ref objectid value, read time tree block corruption detected Inbox
Date: Fri, 27 Dec 2024 15:25:32 -0700	[thread overview]
Message-ID: <87wmfk2277.fsf@gmail.com> (raw)
In-Reply-To: <cfc9177b-ab53-40c2-b627-0045e9348938@gmx.com>

[-- Attachment #1: Type: text/plain, Size: 668 bytes --]

Qu Wenruo <quwenruo.btrfs@gmx.com> writes:

> 在 2024/11/27 09:39, Brett Dikeman 写道:
>> On Tue, Nov 26, 2024 at 4:30 PM Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>>
>>> Inode cache is what you need to clear.
>>
>> Brilliant! Thank you, Qu. It did mount cleanly. Shame Debian's
>> toolchain is so out-of-date. I pinged the maintainer asking if they
>> could pull 6.11.

I've salvaged Debian's btrfs-progs package, so it will now be kept
significantly more up-to-date than it was in the past.  6.12 was just
accepted into unstable/sid, and it will migrate to testing/trixie after
Debian 13's "alpha1" installer is released.

Regards,
Nicholas


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]

      parent reply	other threads:[~2024-12-27 22:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26 16:11 corrupt leaf, invalid data ref objectid value, read time tree block corruption detected Inbox Brett Dikeman
2024-11-26 21:30 ` Qu Wenruo
2024-11-26 23:09   ` Brett Dikeman
2024-11-27  3:17     ` Qu Wenruo
2024-11-30  1:11       ` Nicholas D Steeves
2024-11-30  4:37         ` Qu Wenruo
2024-12-27 22:25       ` Nicholas D Steeves [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=87wmfk2277.fsf@gmail.com \
    --to=sten@debian.org \
    --cc=brett.dikeman@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.