onlyjob

Indeed MooseFS team is amazing, honestly. However unwarranted hostility of @edrock200 completely inappropriate. "Poor setup that does not follow IT 101 principles" is nonsense. Nothing in this issue was a...

One copy of disposable data on reliable storage is not "asking for trouble" but a calculated risk -- a perfectly valid option in some circumstances, when admin knows what he...

I've used the following shell script to find the undergoal file: ``` #!/bin/sh find $@ -xdev -type f -print0 | xargs -0 --no-run-if-empty -P8 -I{} -- \ sh -c '(...

All chunkservers are online and not in maintenance mode, of course. (I had that chunk lingering for several months.)

No, probably not. The file is a log file from `rsnapshot` which is executed once a day by a cron job.

I'll have a look, thanks. The file is a log file that is being appended daily, that's why it have been modified recently. The idea that I may have not...

``` rsnapshot.log: chunk 0: 000000004A77F05D_0000013C / (id:1249374301 ver:316) ; mtime:1758126813 (2025-09-18 02:33:33) copy 1: 192.168.0.194:9422 ; status:WRONG VERSION copy 2: 192.168.0.196:9422 ; status:VALID ``` The chunk is not mentioned in...

No snapshots of that file; there is only one chunk (current file size is `5787337`). The output of `mfsfileinfo` quoted above is complete.

Thank you for your insightful comments and thoughtful ideas of how to troubleshoot. Yes, the affected file is in `archive` storage class, along with over 15 million (fully replicated) files....

I think I finally understood what was blocking repair of this chunk. There are five chunkservers labelled `M` and only one labelled `U`, where `WRONG VERSION` chunk is stuck. Apparently...