Hello!
This is not fixed.
I sampled failing autopkgtests for MariaDB at
https://ci.debian.net/packages/m/mariadb/testing/ppc64el/ between May
7th and 22nd. They still have crashes that include error message
'Database page corruption on disk'. Both failing and passing ones were
running kernel:
Hi Otto,
On Sun, Apr 09, 2023 at 03:30:35PM -0700, Otto Kekäläinen wrote:
> > > > Paul Gevers asked if the issues are gone as well with 6.1.12-1
> > > > (or later 6.1.y series versions, which will land in bookworm). That
> > > > would be valuable information to know as well to exclude we do not
>
> > > Paul Gevers asked if the issues are gone as well with 6.1.12-1
> > > (or later 6.1.y series versions, which will land in bookworm). That
> > > would be valuable information to know as well to exclude we do not
> > > have the issue as well in bookworm.
> >
> > Were you able to verify this?
Hi Otto,
On 09-04-2023 03:54, Otto Kekäläinen wrote:
Paul Gevers asked if the issues are gone as well with 6.1.12-1
(or later 6.1.y series versions, which will land in bookworm). That
would be valuable information to know as well to exclude we do not
have the issue as well in bookworm.
Were
> > On Sat, Mar 18, 2023 at 11:19:29PM -0700, Otto Kekäläinen wrote:
> > > Any updates on this one?
> > >
> > > I am still seeing the main.index_merge_innodb failure in
> > > https://buildd.debian.org/status/fetch.php?pkg=mariadb=ppc64el=1%3A10.11.2-2%7Eexp1=1678728871=0
> > > and rebuild
> > >
Control: tags -1 + moreinfo
Hi
On Sun, Mar 19, 2023 at 05:02:19PM +0100, Salvatore Bonaccorso wrote:
> Hi,
>
> On Sat, Mar 18, 2023 at 11:19:29PM -0700, Otto Kekäläinen wrote:
> > Any updates on this one?
> >
> > I am still seeing the main.index_merge_innodb failure in
> >
Hi,
On Sat, Mar 18, 2023 at 11:19:29PM -0700, Otto Kekäläinen wrote:
> Any updates on this one?
>
> I am still seeing the main.index_merge_innodb failure in
> https://buildd.debian.org/status/fetch.php?pkg=mariadb=ppc64el=1%3A10.11.2-2%7Eexp1=1678728871=0
> and rebuild
>
Any updates on this one?
I am still seeing the main.index_merge_innodb failure in
https://buildd.debian.org/status/fetch.php?pkg=mariadb=ppc64el=1%3A10.11.2-2%7Eexp1=1678728871=0
and rebuild
https://buildd.debian.org/status/fetch.php?pkg=mariadb=ppc64el=1%3A10.11.2-2%7Eexp1=1679174850=0.
Logs
On Mon, 6 Mar 2023 13:25:36 +1100 Daniel Black wrote:
Since revering to linux-image-5.10.0-20 we've been free of the same errors.
On ci.debian.net I upgraded all ppc64el hosts to bookworm on 2023-03-09.
debian@ci-worker-ppc64el-04:~$ uname -a
Linux ci-worker-ppc64el-04 6.1.0-5-powerpc64le #1
Since revering to linux-image-5.10.0-20 we've been free of the same errors.
On Tue, Feb 28, 2023 at 5:24 PM Diederik de Haas wrote:
>
> On Tuesday, 28 February 2023 04:13:18 CET Daniel Black wrote:
> > Source: linux
> > Version: 5.10.0-21-powerpc64le
> > Severity: grave
> > Justification: causes non-serious data loss
> > X-Debbugs-Cc: dan...@mariadb.org
> >
> > >From
On Tuesday, 28 February 2023 04:13:18 CET Daniel Black wrote:
> Source: linux
> Version: 5.10.0-21-powerpc64le
> Severity: grave
> Justification: causes non-serious data loss
> X-Debbugs-Cc: dan...@mariadb.org
>
> >From https://jira.mariadb.org/browse/MDEV-30728
>
> MariaDB's mtr tests on a
Source: linux
Version: 5.10.0-21-powerpc64le
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: dan...@mariadb.org
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you
13 matches
Mail list logo
