Today 13:04~16:19, the regular production of segment files at k1det1 stopped. I could catch this issue quickly because of the slack notification (implemented in klog#32630). The unexpected suspend was caused by the duplication of the frame file in the cache file. Once the list was reproduced properly, the regular segment production started.

Note that when I saw the /frame0, I felt the access was a bit slow. There might have been a issue related to the mount or network, behind.
The duplication in the cache file happened for following frame files: K-K1_C-1424058944-32.gwf, K-K1_C-1424058976-32.gwf, 14240/K-K1_C-1424060256-32.gwf
The correspond times in JST are 2025-02-20 12:55:26 JST and 2025-02-20 13:17:18 JST