Hi Sergei, Thanks for quick reply. You were right. In the new instance, I had the original target partitions within the datadir. After moving it out and checking the file access permissions it started working. In the original setup, it still does not work. Could it be a problem, that the target partitions are on the NFS volume on the Synology NAS? I have checked and rechecked the permissions, and they seems to be correct. Jan On Tue, 20 Feb 2024 at 10:46, Sergei Golubchik <serg@mariadb.org> wrote:
Hi, Jan,
error 140 on *open* (not on create) can basically happen only for two reasons:
* you have a symlinked table and realpath() failed * you have a symlinked table and symlink points into a datadir
make sure all your symlinks are valid and point outside of datadir.
On Feb 20, Jan Křístek via discuss wrote:
Hi,
We have an old instance of MariaDB 10.3.9/10.3.39, with historical data. Every month I copy an old MyISAM partition (binary files) from the same version of the engine (but a different instance) to a big volume and replace an empty partition in the database with symlinks to the newly copied two files (MYD, MYI - when the engine is stopped). I have been doing it for a year or two, checking each time the data are accessible afterwards.
This month it happened, that the data are not accessible anymore, and the database throwing an exception:
*Got error 140: "Wrong create options" from storage engine MyISAM.*
I tried doing it in a new instance, each time I replace a partition with a link to file elsewhere, the error appeared again.
Does anyone have any ideas, why it's showing the error and how to avoid it? I cannot recall changing anything in the database configuration, upgrading any database, or doing any other changes.
Thanks for any help you can provide, Jan
Regards, Sergei Chief Architect, MariaDB Server and security@mariadb.org