Bug 67157
Summary: | Restore VERY slow compared to dump speeds | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | David Stevenson <d.j.stevenson> |
Component: | dump | Assignee: | Mike A. Harris <mharris> |
Status: | CLOSED NOTABUG | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | dledford, sct |
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: | 2002-06-22 06:13:00 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
David Stevenson
2002-06-20 14:21:45 UTC
Arjan, Stephen, Doug: Any suggestions? For the most part, this is limited by tape read speeds. I've seen two things in the past result in *very* slow tape read speeds. 1) Bad tapes that are marginal and result in lots of error recovery actions in order to actually read the data. You can usually tell if this is the case because the tape drive will stop streaming, rewind a bit, then start again and it will do this little backup and retry thing a *lot*. It kills performance and there isn't anything linux can do about it. 2) Writing a tape in a block mode that the tape drive can't read back very well. For example, setting the block size on st0 to 0 then writing to tape and then restoring from that tape may work significantly slower than setting the block size on st0 to 32k and then writing out the backup and then restoring. In this case, the only thing to do is to do a little experimentation with various tape drive settings like block size and compression and perform a backup with each setting and then see how speedily the restore can be done with each setting. Once you find a setting that performs well, stick with it as your default. If neither of these solves your problem, then reopen the bug report. However, until there is something else to go on, this doesn't sound like a bug to me, it sounds like hardware issues. |