looking at this a little more, the first thing i can confirm is that this is definitely a problem with the ISAM code and not the MyISAM code, so what christian suggested (ALTER TABLE) is really the best solution for the time being, as the ISAM table type is deprecated anyway.
also, i'm fairly certain that the problem is with my_create
as christian suggests, but my guess is that it has to do with
the O_EXCL flag and no the O_NOFOLLOW. i believe the O_NOFOLLOW
was inserted in the suspect patch to prevent symlink attacks,
and maybe the coder also put in the O_EXCL not realizing that
it would break the ISAM operations which call my_create on
pre-existing ISM files?
i don't know enough about ISAM to know whether or not this behaviour
is normal and whether or not simply removing such a check would be
the appropriate thing to do. anyway, i'll look into it a little more.
sean
signature.asc
Description: Digital signature
