Should I script removing /tmp/xtrabackup_suspended before nightly innobackupex?

Asked by John Keith Hohm on 2012-05-31

I'm guessing that one night the system crashed while running innobackupex and left the $suspend_file, /tmp/xtrabackup_suspended, on the filesystem. It took a while for me to figure out that this then causes innobackupex to think xtrabackup has suspended itself the moment it starts, and then when xtrabackup actually does suspend itself innobackupex is waiting for it to end and does not re-remove the $suspend_file, leading to a wait deadlock.

A cron job runs innobackupex, and I'm wondering if perhaps I should add removing /tmp/xtrabackup_suspended to the beginning of the job? I'm wondering if there is some inbuilt method for locking out or at least detecting an interrupted, or worse a concurrently running, innobackupex that I should be taking advantage of?

I suppose not even detecting the presence of an already-existing $suspend_file could be considered a bug of sorts in innobackupex?

Question information

Alexey Kopytov (akopytov) said : #1

John,

Agree, it's a bug. Converting to a bug report.

Can you help with this problem?

Provide an answer of your own, or ask John Keith Hohm for more information if necessary.

To post a message you must log in.