Hi, after the release of 6.1 I have to do a "yum clean all" on all my 6.0 machines in order to make yum work again. The reason is that the old CR directory on the mirrors is now empty and the new one isn't used until I actually upgrade the system to 6.1 (or at least the centos-release package).
Isn't there a better way to handle this without breaking yum?
I'm also not quite sure why the "yum clean all" is required. It has been a few days now since 6.1 has been released so shouldn't the cached metadata have been expired by now anyway or is there metadata that has unusually long caching times?
Regards, Dennis
On 12/14/2011 10:53 AM, Dennis Jacobfeuerborn wrote:
Isn't there a better way to handle this without breaking yum?
I am sure there is, looking into that right now
I'm also not quite sure why the "yum clean all" is required.
you should not need to do an 'all' for anything really, 'yum clean metadata' will do what you need here.
- KB
On 12/14/2011 12:30 PM, Karanbir Singh wrote:
On 12/14/2011 10:53 AM, Dennis Jacobfeuerborn wrote:
Isn't there a better way to handle this without breaking yum?
I am sure there is, looking into that right now
posted a potential fix into the metadata, that should peculate through to mirrors soon and fix the issue for everyone.
- KB
On 12/14/2011 01:44 PM, Karanbir Singh wrote:
On 12/14/2011 12:30 PM, Karanbir Singh wrote:
On 12/14/2011 10:53 AM, Dennis Jacobfeuerborn wrote:
Isn't there a better way to handle this without breaking yum?
I am sure there is, looking into that right now
posted a potential fix into the metadata, that should peculate through to mirrors soon and fix the issue for everyone.
Great, thanks! Can you elaborate what the fix changes? This accute problem is no biggie as it has a simple manual solution but if it would be necessary to do this on every distro update that wouldn't be ideal.
Regards, Dennis
On 12/15/2011 07:12 AM, Dennis Jacobfeuerborn wrote:
On 12/14/2011 01:44 PM, Karanbir Singh wrote:
On 12/14/2011 12:30 PM, Karanbir Singh wrote:
On 12/14/2011 10:53 AM, Dennis Jacobfeuerborn wrote:
Isn't there a better way to handle this without breaking yum?
I am sure there is, looking into that right now
posted a potential fix into the metadata, that should peculate through to mirrors soon and fix the issue for everyone.
Great, thanks! Can you elaborate what the fix changes? This accute problem is no biggie as it has a simple manual solution but if it would be necessary to do this on every distro update that wouldn't be ideal.
The issue was that we use a hard linker on our mirrors (to save space) ... so if 2 (or more) files have the same CRC info, they are linked to the same physical file.
The hard linker found that all the "zero RPMs in a repo" metadata was the same and hard linked them all together ... but the "Date" on those metadata files was older than the date on the 6.0 CR repo files.
So, if you had cached CR metadata, the system thought it was newer than the current metadata, and therefore did not replace it.
We just recreated the metadata to be a newer date than the 6.0 CR metadata and that fixed the issue.
-
Dennis Jacobfeuerborn -
Johnny Hughes -
Karanbir Singh