Hi, I've noticed that BLKTRACESETUP sometimes fails with an error message if a previous instance of blktrace was killed e.g. with SIGKILL (though sometimes it happens when it is killed with SIGTERM). An easy fix is to call BLKTRACESETUP in a loop: if BLKTRACESETUP fails, we can call BLKTRACESTOP and BLKTRACETEARDOWN and try BLKTRACESETUP again. Does this sound reasonable? Thanks, Souvik Banerjee -- To unsubscribe from this list: send the line "unsubscribe linux-btrace" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html