chris at czar
Aug 4, 2012, 9:18 PM
Post #3 of 3
On 5/08/2012 1:57 PM, Michael T. Dean wrote:
> On 08/04/2012 09:43 PM, Chris Nicholls wrote:
>> Morning everyone,
>> I have a problem that I'm after advise. Short version, one HD died,
>> caused problems, now removed, corrupted DB. Running myth_optimize_db
>> rapidy fills the harddisk to 100% and stops. It looks like
>> logging.MYD and logging.TMD now fill the disk. Total size for
>> mythconverg is 5.3G. Is this correct and what can I do?
> A TMD file is a temporary MySQL data file that's used when rebuilding
> indices or repairing tables. It sounds like (and makes sense that)
> your logging table was corrupted, so it's trying to repair it, but you
> don't have enough space for it to complete the repair.
> As a workaround, try:
> mysql -umythtv -p mythconverg -e 'TRUNCATE TABLE logging;'
> and if it completes successfully, delete any orphaned TMD file, then
> re-try the repair.
> mythtv-users mailing list
> mythtv-users [at] mythtv
Thankyou work a treat, first time.
mythtv-users mailing list
mythtv-users [at] mythtv