On Fri, Jul 14, 2023 at 09:49:04AM -0400, Neal Gompa wrote: > On Fri, Jul 14, 2023 at 8:48 AM Florian Weimer <fweimer@xxxxxxxxxx> wrote: > > > > * Miroslav Suchý: > > > > > Dne 14. 07. 23 v 13:53 Florian Weimer napsal(a): > > >> What about impact beyond the builders? > > >> > > >> Are end users are expected to do this? Do we have a tool for this? > > > > > > Close to zero. You have to do a really lots of builds. And keep the > > > buildroots of these (failed) builds. > > > > This is not restricted to mock or Koji, though. There just needs to be > > one application that creates and deletes many files (or produces other > > events that causes object ID allocation in btrfs). > > > > For me it's going to be slow enough that the file system will likely be > > recreated before I encounter the 31-bit object ID limit. But I wonder > > if that's true for everyone. > > > > I don't know of a 32-bit workload that would trigger this reliably and > reasonably quickly, but if there is one, then I would be interested in > knowing about it. The 32-bit binary is what suffers the consequences. The workload that /causes/ the problem can be anything which creates lots of files. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
