FileSystem.truncate returns false (no exception) but the file is never closed and not writable after this.
It seems to be because of copy on truncate which is used because the system is in upgrade state. In this case a rename between devices is attempted.
See attached log and repro code.
Probably also affects truncate snapshotted file when copy on truncate is also used.
Possibly it affects not only truncate but any block recovery.
I think the problem is in updateReplicaUnderRecovery
blockFile is created with copyReplicaWithNewBlockIdAndGS which is allowed to choose any volume so rur.getVolume() is not where the block is located.