On 17/03/2021 03.41, L A Walsh wrote:
On 2021/03/16 12:53, Carlos E. R. wrote:
One of the moves (across mounts) failed because target directory was not empty.
Um. How would it not being across a mount make it different?
A move in the same mount is done rewriting inodes or whatever, not moving the actual data sectors. It happens fast even with huge files. Across mounts the data has to be copied, then the source deleted. I remember that when rpms first tried moves and it happened to be across mounts, it aborted. After sopme bugzillas, these cases were cared for, and "same mount" was not assumed. But this was not the case, rather more complicated as Andrei explains. Wow, what a thing. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)