From: Niklas Cassel <cassel@kernel.org>
To: Hank Barta <hbarta@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: "ata2.00: Enabling discard_zeroes_data" in dmesg 1/minute
Date: Mon, 31 Aug 2026 09:42:55 +0200 [thread overview]
Message-ID: <apUwf-BOc0pJe3Ic@ryzen> (raw)
In-Reply-To: <CABTDG8-3oiR+P7ebTx2PY-OQNGoMod3CRSk9uMaTHKW4FnRKbA@mail.gmail.com>
Hello Hank,
On Fri, Jul 31, 2026 at 02:11:56PM -0500, Hank Barta wrote:
> Good afternoon,
> This message is being posted to the kernel ring buffer 1/minute on one
> of my servers. I just spent a few minutes with ChatGPT tracking this
> down and ChatGPT has suggested that it may be due to a regression in
> libata. Full details of the interaction can be viewed at
> https://chatgpt.com/share/6a6cef79-9bac-83ea-86d6-5de28f09e70a
>
> As near as I can tell, the message is harmless aside from flushing the
> kernel rung buffer. Some brief details regarding this host:
>
> Debian Trixie
> Linux oak 6.12.96+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.96-1
> (2026-07-20) x86_64 GNU/Linux
> ZFS version zfs-kmod-2.3.2-2
>
> I searched to see if this had already been reported and found nothing,
> though that might reflect more WRT my search capabilities.
>
> Is this something I should submit as a bug? If so, kernel bug list or Debian?
>
> I appreciate instructions for how best to proceed if I can be of any
> assistance. (And if that's "go away" I will take no offense.)
ZFS is an out of tree filesystem incompatible with the license used by
Linux, thus we don't spend any time looking into issues related to ZFS.
If you can reproduce the error with any filesystem included in Linux,
please send an email that includes your full details in the email itself
(rather than linking to an URL).
Kind regards,
Niklas
prev parent reply other threads:[~2026-08-31 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 19:11 "ata2.00: Enabling discard_zeroes_data" in dmesg 1/minute Hank Barta
2026-08-31 7:42 ` Niklas Cassel [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=apUwf-BOc0pJe3Ic@ryzen \
--to=cassel@kernel.org \
--cc=hbarta@gmail.com \
--cc=linux-ide@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 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.