fedora mirrors need hardlink support
Bug #545666 reported by
Robert Collins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| lmirror |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
http://
So we'll want hardlink support eventually.
Some early thoughts:
- new hardlinked content is easy, as long as it doesn't link to existing files. (compare inodes during mirror process)
- incrementally linked content is much trickier - need to correspond with the fedora folk and find out if this would be needed, or if punting would be good-enough.
| tags: | added: fedora rpm yum |
| Changed in lmirror: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
Revision history for this message
| Robert Collins (lifeless) wrote | #1 |
To post a comment you must log in.
Some notes about the needs here -
x86_64 repositories may have i386 packages hardlinked to i386 repositories; they would be both added in the same push.
At release time, a (roughly) cp -al prerelease release takes place, which offers a lot of opportunity for hardlinking - and that would be to existing content.
So we probably want to build a hash->path index of existing content when scanning for changes, so that we can get a list of paths to check for hardlinks [or even infer new hardlinks.