[mythtv-users] MySQL recordedseek regularly getting corrupted

[Jean-Yves Avenard]

On 1 December 2016 at 00:22, Michael T. Dean <mtdean at thirdcontact.com> wrote:

> Are you sure your MySQL temp directory is on the file system that has
> sufficient space?

yes..

There's always about 56GB left on the SSD, I only have a / partition
(and /home but being btrfs all partitions have the same free space
amount)

>
> https://dev.mysql.com/doc/refman/5.7/en/temporary-files.html
>
> Also, note that things are handled differently with InnoDB versus MyISAM
> storage engines (as explained in the link, above).  Might want to check:
>
> SHOW VARIABLES LIKE '%tmpdir%';

mysql> SHOW VARIABLES LIKE '%tmpdir%';
+-------------------+-------+
| Variable_name     | Value |
+-------------------+-------+
| slave_load_tmpdir | /tmp  |
| tmpdir            | /tmp  |
+-------------------+-------+
2 rows in set (0.00 sec)

/tmp as such is on the / partition, which has 56GB free.

>
> to see if that gives any hints as to what's happening.  Though if the temp
> file error was just myisamcheck , that may just be because you weren't in
> your MySQL data directory when you ran it?

The error about the inability to create a temp file is given by
mysqlcheck --repair mythconverg -u root -p
at the time / had 56GB free.
I could reproduce consistently doing mysqlcheck --repair mythconverg -u root -p
I always get a temp error regardless of free disk space.

myisamcheck is obviously run inside the /var/lib/mysql/mythconvert
directory. It's the only command that works that will then make
mysqlcheck succeed.