Bug 106514
Summary: | rpm -F from amd-mounted NFS may remove packages from database | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alexandre Oliva <oliva> |
Component: | rpm | Assignee: | Jeff Johnson <jbj> |
Status: | CLOSED WONTFIX | QA Contact: | Mike McLean <mikem> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | michael-ring |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-10-18 20:13:46 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alexandre Oliva
2003-10-07 22:00:51 UTC
rpm opens the files from the CLI twice, first to check dependencies, later to actually install. If amd umounts in between, then, yes, the packages cannot be reopened, and the upgrade will fail in peculier ways. Don't do that is the best answer I got. Reopening original pkgs is necessary for anaconda to remount install media, and is unlikely to be changed. Keeping file descriptors open has been known to run out of file descriptors (although limits are probably larger these days). See, I don't have much of a problem if it fails, but I think it's a major problem that it ends up *removing* the packages that were meant to be replaced, instead of leaving them alone. The point at which the original package is reopened is after all checks on package content have been performed. The attempt to upgrade is final. Any failure after the checks can/will have irreversible side effects, either partially installed packages, or, in this case package erasures. Don't install from automounted NFS is the answer. Does this mean that an unexpected reboot in the middle of an upgrade could have results that are just as disastrous? Yes. Failures of package scriptlets too, Then there's kill -9 ... ENOSPC makes a bloody mess as well, space is checked before entering install state machine, leaving a largish window. rpm has never provided any of the traditional database commit semantics, never has, never will. Sh*t happens, up to the user to clean up the mess afterwards, or avoid siturations like NFS automounts. I see. Thanks for the clarification. I guess I was just expecting too much from it :-( *** Bug 108691 has been marked as a duplicate of this bug. *** |