Bug 57570
Summary: | ext3/unmap kernel panic during glibc upgrade | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Alexandre Oliva <aoliva> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:39:19 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
2001-12-16 07:12:52 UTC
P3/500, ASUS P2B-F, RH7.1, ext2, rest of partitions ext3, all Seagate IDE disks. The upgrade to the new glibc errate ruined my system. Could not ls, su, anything afterwards, everything coredumped. Rebooting failed - spawning processes to fast at each runlevel and running out of them so hard it wasn't even possible to ctrl+alt+del. It was also impossible to boot into linux single. The whole installation was effectively trashed, i had to reinstall from scratch on a new disk. The files were downloaded from a 7.1 update mirror and upgraded manually. Signatures were OK. A following upgrade of all errata via up2date then went fine on a pure ext2 system, apart from up2date refusing to upgrade "filesystem" because it was "read only" - it seemed it was looking for it on a CD?? The old disks are mountable and AOK after reinstall on another disk, but the installation is broken, i can't boot from them. Nothing to see in the old logs. Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |