Bug 220735
Summary: | rpm seqfault in rescue image in VMware | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Eugene Kanter <ekanter> |
Component: | rpm | Assignee: | Panu Matilainen <pmatilai> |
Status: | CLOSED NEXTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-08-10 13:08:59 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
Eugene Kanter
2006-12-25 05:37:12 UTC
rpm runs under VMware, there's nothing wrto segfaults running FC6 under VMware. The issue is likely the instabilities introduced by yum reopening an rpmdb thousands of times per transaction, see many many other bugs against rpm in FC6. Before submitting this I read all FC6 related rpm bugs, there are many segfault reports but all of them are in OS environment and not in rescue. Let me repeat: I can run rpm install and query commands, yum updates and erases in VMware without any issues whatsoever. However no rpm command work if rescue image booted in the same VMware environment. My impression was that rescue image environment (e.g. kernel, libc, etc.) is the same as real OS. Isn't it? What are the symptoms of "no rpm command works" with rescue mode in VMware? Do rm -f /var/lib/rpm/__db* to get rid of any stale locks or corrupted caches first. Try running with -vv and attach the output of any failed command here. NEEDINFO IIRC the kernel in FC6 the installer/rescue image is bugged with the kernel mmap() corruption issue. Not much that can be done about the released isos... The fact that you're not seeing it on installed systems doesn't necessarily mean that much, took a while before I was able to reproduce the mmap() bug on any of my systems back then. And once updates have been installed the issue will be gone again, but no updates in rescue-mode. If F7 rescue image fails similarly within VMware, then it's likely to be something else instead (in which case feel free to reopen against devel). |