I also experience a difference between files advertised in fedora-buffet/fedora/fullfiletimelist-fedora and content avaialble for rsync:
[bellet@mandril fedora]$ rsync download-cc-rdu01.fedoraproject.org::fedora-buffet/fedora/linux/development/33/Everything/aarch64/iso/ --no-motd drwxr-xr-x 211 2020/10/22 16:56:34 . -rw-r--r-- 203 2020/10/22 14:24:13 Fedora-Everything-33-aarch64-20201022.n.0-CHECKSUM -rw-rw-r-- 669,405,184 2020/10/22 09:47:26 Fedora-Everything-netinst-aarch64-33-20201022.n.0.iso -rw-r--r-- 285 2020/10/22 11:10:01 Fedora-Everything-netinst-aarch64-33-20201022.n.0.iso.manifest
and
[bellet@mandril fedora]$ rsync download-cc-rdu01.fedoraproject.org::fedora-buffet/fedora/fullfiletimelist-fedora ~/fullfiletimelist-fedora -avHS --no-motd receiving incremental file list fullfiletimelist-fedora sent 43 bytes received 209,162,652 bytes 22,017,125.79 bytes/sec total size is 209,111,488 speedup is 1.00 [bellet@mandril fedora]$ grep Fedora-Everything-netinst-aarch64-33-20201023.n.0.iso ~/fullfiletimelist-fedora 1603460116 f 285 linux/development/33/Everything/aarch64/iso/Fedora-Everything-netinst-aarch64-33-20201023.n.0.iso.manifest 1603460130 f 669368320 linux/development/33/Everything/aarch64/iso/Fedora-Everything-netinst-aarch64-33-20201023.n.0.iso
The file lists are generated asynchronously from any filesystem changes. I would not expect them to always exactly match the current content.
Now, if content is persistently missing then that points to an actual issue.
The problem seems to be that fullfiletimelist-fedora contains stuff not yet available on the filesystem (ie more recent according to the date in the filename). It looks like fullfiletimelist-fedora is rsynced first, and content is rsynced after.
This issue is also specific to download-cc-rdu01 FWIW.
It's almost certainly in the process of copying data over, and it's quite possible that it has the new file lists but not all of the content yet.
I will have to see if there is any way I can minimize the possibility of this happening within quick-fedora-mirror. rsync is already supposed to be using delayed updates for everything and so all of the new content should appear "quickly" at the end of the transfer. In any case, that won't be something to be handled in an infrastructure ticket.
These should be in sync now? can you confirm?
Yes, they are in sync now.
Metadata Update from @zlopez: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.