Bug 88159
| Summary: | Umount problem after prelink -avm | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Sepp Rudel <sepprudel> |
| Component: | prelink | Assignee: | Jakub Jelinek <jakub> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | ||
| 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: | 2003-10-06 07:31:34 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: | |||
Does telinit u after prelink -avm help? Without that, /sbin/init is still using the old copy of libc and thus the root is really busy. But of course! telinit u solved the problem. Perhaps this could be mentioned on the man page, there was some noise about this amongst the Debian tribe IIRC. FWIW, I can now reproduce this naturally with: prelink -au reboot prelink -avm reboot [etc] prelink 0.3.0-1 and later (ATM 0.3.0-6) should deal with it in the cron script which does the prelinking automatically. |
Description of problem: After installing RH9 (and betas that preceeded it) and running prelink -avm causes following error during next boot: umount: /: device is busy If the same command is run later, no error appear. Version-Release number of selected component (if applicable): prelink coming with RH9. How reproducible: Steps to Reproduce: 1. Install RH9 2. Run prelink -avm 3. Reboot and look at the messages Actual results: umount gives errors. Expected results: umount goes ok. Additional info: I know the instructions to reproduce are PITA and it may well be that prelinking some certain files is the cause but since I don't have a slightest clue what it might be, I won't iterate this. However, as noted above, I've noticed this same behaviour with RH9, and every 8.0.9x betas. Probably with RH8, too, IIRC.