public inbox for [email protected]
 help / color / mirror / Atom feed
From: Xan Charbonnet <[email protected]>
To: Jens Axboe <[email protected]>,
	Salvatore Bonaccorso <[email protected]>,
	Pavel Begunkov <[email protected]>
Cc: [email protected], Bernhard Schmidt <[email protected]>,
	[email protected], [email protected],
	[email protected]
Subject: Re: Bug#1093243: Upgrade to 6.1.123 kernel causes mariadb hangs
Date: Mon, 27 Jan 2025 10:38:53 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

The MariaDB developers are wondering whether another corruption bug, 
MDEV-35334 ( https://jira.mariadb.org/browse/MDEV-35334 ) might be related.

The symptom was described as:
the first 1 byte of a .ibd file is changed from 0 to 1, or the first 4 
bytes are changed from 0 0 0 0 to 1 0 0 0.

Is it possible that an io_uring issue might be causing that as well? 
Thanks.

-Xan


  reply	other threads:[~2025-01-27 16:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <173706089225.4380.9492796104667651797.reportbug@backup22.biblionix.com>
     [not found] ` <[email protected]>
     [not found]   ` <[email protected]>
     [not found]     ` <[email protected]>
2025-01-23 20:05       ` Bug#1093243: Upgrade to 6.1.123 kernel causes mariadb hangs Salvatore Bonaccorso
2025-01-23 20:26         ` Jens Axboe
     [not found] ` <[email protected]>
2025-01-23 20:49   ` Salvatore Bonaccorso
2025-01-23 23:20     ` Pavel Begunkov
2025-01-24  2:10       ` Xan Charbonnet
2025-01-24  5:24       ` Salvatore Bonaccorso
2025-01-24 10:33         ` Pavel Begunkov
2025-01-24 16:30           ` Xan Charbonnet
2025-01-24 18:40             ` Pavel Begunkov
2025-01-24 20:33               ` Salvatore Bonaccorso
2025-01-24 20:51                 ` Jens Axboe
2025-01-26 22:48                   ` Xan Charbonnet
2025-01-27 16:38                     ` Xan Charbonnet [this message]
2025-01-27 17:21                       ` Pavel Begunkov
2025-01-27 16:49                     ` Pavel Begunkov

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=dfc6006d-10cf-4090-aafd-77d62c341911@charbonnet.com \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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