After emerging coreutils-5.94-r1 without incident, I noticed unusual output from mv when I moved a directory of a number of large files on one disk to a directory on another disk, i.e., a move across filesystems. Instead of silently moving the files like every version of mv I've used in the past five years, mv emitted what appeared to be progress information for *some* of the files being transferred. It looked like this: jack@asus - 21:00:01 - [ ~ ] 3-0-512 $> mv /dead/unfiled/gd77-05-11.32274 /dead/filed/1977 770511107.mp3 | 100% | 9 MiB | 3580 KiB/s | ETA 00:00.01 770511104.mp3 | 100% | 12 MiB | 8432 KiB/s | ETA 00:00.00 770511109.mp3 | 100% | 7133 KiB | 228 KiB/s | ETA 00:00.30 770511301.mp3 | 100% | 14 MiB | 3720 KiB/s | ETA 00:00.02 770511210.mp3 | 100% | 12 MiB | 3316 KiB/s | ETA 00:00.03 770511201.mp3 | 100% | 5343 KiB | 1508 KiB/s | ETA 00:00.02 770511206.mp3 | 100% | 8197 KiB | 1252 KiB/s | ETA 00:00.05 Twenty-six files were moved, but only seven had progress information displayed. Is this a feature or a bug? Like I said, I've been using mv in exactly this way for years, and this is the first time I've ever seen it exhibit this behavior. This behavior is reproducible, but the files for which progress information is displayed seem to change with each transfer.
it's a bug ... the progress bar should *only* show up when using -g
well, according to original author, this is by design ... but i consider it a bug so i'll clean up the code ;)
ive cleaned up the patch in 5.94-r3 ... give it a spin please
