@sa2000 The file I attached is the first 15,000 lines of the 35GB file. The rest of the file is the same line (qscale == 0) repeated endlessly. The process had stuck in an infinite loop writing that line to the log.
It was 35GB when I noticed it and was still growing when I manually killed the process. I truncated it to 15,000 lines because there’s no additional information in the log file, it’s just the same line repeated until the disk fills up.
So it is the same issue, it’s just that in my case I caught it before it filled the disk because it takes a while to fill up 16TB.
@almdlm said: @sa2000 The file I attached is the first 15,000 lines of the 35GB file. The rest of the file is the same line (qscale == 0) repeated endlessly. The process had stuck in an infinite loop writing that line to the log.
It was 35GB when I noticed it and was still growing when I manually killed the process. I truncated it to 15,000 lines because there’s no additional information in the log file, it’s just the same line repeated until the disk fills up.
So it is the same issue, it’s just that in my case I caught it before it filled the disk because it takes a while to fill up 16TB.
I will push for it to be progressed regardless
Our testing of the file resulted in the log not going beyond 35Gb
I don’t know if it’s still useful, but my system didn’t fail again for several weeks. I can likely upload the .ts and relevant log snippets somewhere, if still needed.
