[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <999aeda3-5565-44a3-96d4-00dcd91a4cbd@gmail.com>
Date: Mon, 27 Jan 2025 17:21:15 +0000
From: Pavel Begunkov <asml.silence@...il.com>
To: Xan Charbonnet <xan@...rbonnet.com>, Jens Axboe <axboe@...nel.dk>,
Salvatore Bonaccorso <carnil@...ian.org>
Cc: 1093243@...s.debian.org, Bernhard Schmidt <berni@...ian.org>,
io-uring@...r.kernel.org, linux-kernel@...r.kernel.org,
regressions@...ts.linux.dev
Subject: Re: Bug#1093243: Upgrade to 6.1.123 kernel causes mariadb hangs
On 1/27/25 16:38, Xan Charbonnet wrote:
> 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.
The hang bug is just that, waiters not waking up. The completions
users get back should still be correct when they get them, and it's
not even close to code that might corrupt data.
I believe someone mentioned corruption reports from killing the hang
task, I'd assume it should tolerate even sigkills (?). It's much more
likely it's either some other kernel or even io_uring issue, or the
db doesn't handle it right since the update. For that other report,
did they update the kernel? I don't see a dmesg log in the report,
that could also be useful to have in case some subsystem complained.
--
Pavel Begunkov
Powered by blists - more mailing lists