Hi Jan,
the root cause for the corruption, we know: NFSv4 bugs. The
"dump/restore-to-new-db" path we know as well.
My question here is: is there a way to get rid of this table _without
restoring to a new DB_.
thanks,
martin
On Wed, Jan 28, 2015 at 2:05 AM, Jan Lindström
wrote:
> Hi,
>
> Yes
Hi Jan,
thanks for your notes. I have gone through the instructions in that
doc link, but they do not help. In the prior emails I have included
stack dumps and straces of what happens when I follow those
instructions.
There is something else going on, or perhaps a regression that
prevents the pro
More information. Two actions attempted: dropping the table, removing
the table on disk and trying to recreate it.
=DROP TABLE trace=
Only the ibd file is in place. I stop mariadb, restore the frm file,
start mariadb, try "drop table", I get
MariaDB [moodle_sand]> drop table mdl_tag_correlation
Hi Folks,
We run a very large infra on MariaDB/RHEL6.x/RHEV/NetApp; thousands of
VMs, each running MariaDB and very busy. MariaDB is 5.5.32.
We recently had some NFS problems which led to minor DB corruption.
Luckily, the corruption was isolated to a table holding cache data,
and in fact one that
4 matches
Mail list logo
