Comments on: Can’t always be the hero http://blog.xcski.com/2007/03/02/cant-always-be-the-hero Everything I used to bore people on newsgroups and mailing lists with, now in one inconvenient place. Fri, 05 Dec 2008 10:36:44 +0000 http://wordpress.org/?v=2.6.5 By: Keith http://blog.xcski.com/2007/03/02/cant-always-be-the-hero#comment-18180 Keith Fri, 02 Mar 2007 17:15:04 +0000 http://blog.xcski.com/2007/03/02/cant-always-be-the-hero#comment-18180 In my experience, you need an occasional failure to help manage expectations (others, not yours). Once you get a reputation for pulling people's chestnuts out of the fire, they will expect it from you. Not only that, but they will be less careful, since they know you will be there to save them when they screw up (again). In my experience, you need an occasional failure to help manage expectations (others, not yours). Once you get a reputation for pulling people’s chestnuts out of the fire, they will expect it from you. Not only that, but they will be less careful, since they know you will be there to save them when they screw up (again).

]]> By: Paul Tomblin http://blog.xcski.com/2007/03/02/cant-always-be-the-hero#comment-18174 Paul Tomblin Fri, 02 Mar 2007 12:22:37 +0000 http://blog.xcski.com/2007/03/02/cant-always-be-the-hero#comment-18174 James, the bug you reference wasn't introduced until 2.6.18. We've been seeing rpm lockups since we started with 2.4.x in RedHat 7.3. The bug I'm referring to is, if I remember correctly, an in-memory locking system that IBM wrote that if it deadlocks there is no way to fix short of rebooting. James, the bug you reference wasn’t introduced until 2.6.18. We’ve been seeing rpm lockups since we started with 2.4.x in RedHat 7.3.

The bug I’m referring to is, if I remember correctly, an in-memory locking system that IBM wrote that if it deadlocks there is no way to fix short of rebooting.

]]> By: James Wilkinson http://blog.xcski.com/2007/03/02/cant-always-be-the-hero#comment-18173 James Wilkinson Fri, 02 Mar 2007 11:41:00 +0000 http://blog.xcski.com/2007/03/02/cant-always-be-the-hero#comment-18173 Experience on the Fedora lists suggests that it might not be a RPM bug, but a kernel bug that has been fixed during the 2.6.19 timeframe. <a href="http://lwn.net/Articles/215868/#Comments" rel="nofollow">This bug</a> may or may not be the culprit, but was found at about the right time, affects Berkeley databases, and is plausible. Since fixed Fedora kernels came out, the only complaints about RPM database corruption have come from people who were running old kernels. I don't know if this could help you... Experience on the Fedora lists suggests that it might not be a RPM bug, but a kernel bug that has been fixed during the 2.6.19 timeframe.

This bug may or may not be the culprit, but was found at about the right time, affects Berkeley databases, and is plausible.

Since fixed Fedora kernels came out, the only complaints about RPM database corruption have come from people who were running old kernels.

I don’t know if this could help you…

]]>