Hi!
>>>>> "Yuri" == Yuri Dario <mc6530@stripped> writes:
Yuri> Hi Monty,
Yuri> the 'check table' is failing because of a RDLCK lock on the index file.
>> From the trace
<cut>
Yuri> I don't see unlocking calls in this block of tracing.
Yuri> T@4 : | | | | >my_pwrite
Yuri> T@4 : | | | | | my: Fd: 12 Seek: 0 Buffer: d2d654 Count: 176
Yuri> MyFlags: 132
Yuri> T@4 : | | | | | error: Write only -1 bytes
Yuri> T@4 : | | | | <my_pwrite
Yuri> T@4 : | | | | error: message: 43 when updateing keyfile
Yuri> so write() is failing.
Yuri> So I need to unlock file before calling my_pwrite(), or stay with
Yuri> current locking code (which doesn't make difference between F_RDLCK and
Yuri> F_WRLCK).
You are right; We added that even if we just check the table, MySQL
will write some status to the header file; We don't need to protect
this with a write lock, as it's not important if we loose this
information.
The fix is probably to lock tables with write locks when doing CHECK
TABLE and running under OS2.
Regards,
Monty
