Bug 254
Summary: | dump failure--slave children out of sync | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | dhunt |
Component: | dump | Assignee: | David Lawrence <dkl> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.2 | ||
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: | 1999-01-14 18:35:29 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
dhunt
1998-12-01 22:40:07 UTC
DUMP: pid=3963 master/slave protocol botched. ^^^^^^^^^^^^ This leads me to believe that there are some possible issues between dump and the timing of process/thread creation on the Sparc systems. At this point, it doesn't look like and tape read/write cycles have yet been started, and the disk read stuff has already worked properly (pass I and II). So, I would suggest looking into the master/slave creation/syncronization code in dump first. There is also the issue of a possible race condition in the kernel due to the drive sub-system and SMP combination. Compiling as UP and/or slowing down the drive might make a difference and would be worth testing out to make sure. Recommended course of action, the user needs to let us know if compiling UP kernel makes a difference. If not, then we can look into the dump code. If it does, then the problem would seem similar to another known SMP problem in 2.0.36 and is not likely to be fixed given the pre-emminent release of 2.2.0. Sorry, replace Sparc with Intel in my last comments.... |