Bug#306409: mysql-server: Security upgrade to package broke delete operations

2005-04-29 Thread Christian Hammers
Hello

 mysql delete from tbl_Country;
 ERROR 1: Can't create/write to file './journals/tbl_Country.ISM'
 (Errcode: 17)

First update: The offending changes are within the big 
  debian/patches/SECURITY__CAN-2005-0709,0710,0711.diff
file. Unpatching just this one makes mysqld work again. From looking at 
it the 
  my_create(.., O_NOFOLLOW,..)
seems suspicious, maybe a DELETE uses symlinks for temporary tables or
something like that.

(more later, lunch break is over now...)

bye,

-christian-



pgpHUhJ6vB1Ky.pgp
Description: PGP signature


Bug#306409: mysql-server: Security upgrade to package broke delete operations

2005-04-29 Thread Christian Hammers
Hello

On 2005-04-26 Mike Brodbelt wrote:
 mysql delete from tbl_Country;
 ERROR 1: Can't create/write to file './journals/tbl_Country.ISM'
 (Errcode: 17)

Update: It is isam/create.c. Just re-adding the O_TRUNC that looked like
beeing forgotten seems not to be enough. I will ask MySQL for an idea.

bye,

-christian-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#306409: mysql-server: Security upgrade to package broke delete operations

2005-04-26 Thread Christian Hammers
tags 306409 + confirmed woody
thanks

Hello Mike

On 2005-04-26 Mike Brodbelt wrote:
 After upgrading this package from security.debian.org, the delete
 operation (at least) has broken. I have a cron job which deletes all
 data in certain tables, and repopulates them from an external data
 source. This is achieved by simply doing delete from tbl_foo, and this
 operation now fails with the following error.
 
 mysql delete from tbl_Country;
 ERROR 1: Can't create/write to file './journals/tbl_Country.ISM'
 (Errcode: 17)

The bug is reproducible. As a quick workaround I can suggest you to
upgrade your tables to the MySQL format (which is better and the default
anyway) using ALTER TABLE xyz TYPE=MyISAM;.

 Tagged as important as a security update has effectively caused a severe
 breakage in the operation of the database for me, and I'm still trying
 to figure out what's changed. There have been no other changes to system
 setup or configuration.

I will browse through the changesets in the next days to see if there's a
but in them.

bye,

-christian-


pgpXmFHCwEQ3Q.pgp
Description: PGP signature