I got the correct answer and I know many people will be responding and I
want to thank them too.
My original question was:
Sun Managers:
I have an ultra 2 running Solaris 2.6. When I run "ufsdump 0uvf /dev/rmt/0mn
/dev/rdsk/c0t0d0s0",
I get the following error and keeps on saying NEEDS ATTENTION:.......... .
Is there anything I am missing or are there any know patches
for ufsdump which can fix this problem. I will summarize. Thanks.
DUMP: Writing 32 Kilobyte records
DUMP: Date of this level 0 dump: Thu Sep 10 11:39:31 1998
DUMP: Date of last level 0 dump: the epoch
DUMP: Dumping /dev/rdsk/c0t0d0s0 (tigershark:/) to /dev/rmt/0mn.
DUMP: Mapping (Pass I) [regular files]
DUMP: Mapping (Pass II) [directories]
DUMP: Estimated 154196 blocks (75.29MB).
DUMP: Dumping (Pass III) [directories]
DUMP: Dumping (Pass IV) [regular files]
DUMP: Finished writing last dump volume
DUMP: Starting verify pass
DUMP: Verification error 61 feet into tape 1
DUMP: NEEDS ATTENTION: Do you want to rewrite?: ("yes" or "no")
DUMP: NEEDS ATTENTION: Do you want to rewrite?: ("yes" or "no") yes
DUMP: This tape will be rewritten and then verified
DUMP: Change Volumes: Mount volume `#1' on `tigershark:/dev/rmt/0mn'
DUMP: NEEDS ATTENTION: Is the new volume (#1) mounted on
`tigershark:/dev/rmt/
0mn' and ready to go?: ("yes" or "no") yes
DUMP: Dumping (Pass III) [directories]
DUMP: Dumping (Pass IV) [regular files]
DUMP: Finished writing last dump volume
DUMP: Starting verify pass
DUMP: Verification error 8 feet into tape 1
DUMP: NEEDS ATTENTION: Do you want to rewrite?: ("yes" or "no") yes
----------------------------------------------------------------------------
----------------------------
I had a great response.
Thanks for the following people who responded.
Bismark Espinoza and James E. Coby pointed me in hte right direction. Both
responded not to use the "v" option.
This made the dump to work.
Manjeet S Rekhi [rekhims@ecae.stortek.com]
MaryEllen Yager [mey@bbt.com]
Bismark Espinoza [bismark@alta.jpl.nasa.gov]
foster@bial1.ucsd.edu
David Evans [DJEVANS@au.oracle.com]
Esaie Vermilus [vermiles@hawk.dehavilland.ca]
Thomas Lester [tlester@spain.iakom.com]
Brian Exelbierd [bcexelbi@controller.osc.state.nc.us]
Michael J. Connolly [mjconnly@newton41.ckcorp.com]
James.E.Coby.Jr@cdc.com
Ford,Andy [andyford@AGEDWARDS.com]
*******************************************************************
Correct response which worked.
Hello,
1. Remove the v from the ufsdump line. You are telling it to
verify the inodes etc which are changing . It doesnt mean verbose
which one would think.
2.Get rid of the "v"
***********************************************************************
Other responses:
3. Have you tried changing the tape and/or cleaning tape-drive heads ?
It looks like tape is having problem reading/verifying the media.
4. HI...try a new tape...
5.Two things I would try:
1. different tape (perhaps different length);
2. clean the tape drive with a cleaning tape and retry
6. Varad,
Depending on the message you either need to change tapes or clean the
tape drive. In your case:
DUMP: Verification error 61 feet into tape 1
DUMP: NEEDS ATTENTION: Do you want to rewrite?: ("yes" or "no")
7. looks like a bad tape or dirty tape drive. If this keeps happening
I would also see about servicing/replacing the drive itself.
8. Hi
Looks like that there's not enough space
on the tape drive. Did you rewind it first?
9. It looks like you are at the end of the tape. Is there any reason why
you
are using 0mn? The "n" means you don't want to rewind the tape at the end
of the backup. So, if you backed up with 0mn on Monday, then Tuesday is
going to pick up at the end of Monday's backup because the tape was never
rewound. If you want to write over the tape on each backup just use 0m.
10.If you are backing up multiple filesystems on one tape do AND will wipe
over it the next backup on the same tape use this format for example:
ufsdump 0uvf /dev/rmt/0mn /
ufsdump 0uvf /dev/rmt/0mn /usr
ufsdump 0uvf /dev/rmt/0mn /etc
ufsdump 0uvf /dev/rmt/0m /var
In the above, each filesystem is dumped on after another on the tape.
After the last filesystem the tape is rewound.
If you want to rewind the tape and try it again issue this command:
# mt -f /dev/rmt/0 rewind
Then try it again.
-t
11.I believe this is indicative of a physical media failure on your tape. I
had a
tape do something similar last month so I chucked it in the bin. Let me
know if
I threw away a perfectly good tape please.
12.Greetings,
How long has it been since you ran a cleaning cartridge through your tape
drive? I got the same error 2 weeks ago - did a cleaning - and my problem
went away. Good luck.
13. last time I saw that message the tape heads needed cleaning.
----------------------------------------------------------------------------
----------------------------
Varad Rajan
Sr. System Analyst
L.A. Cellular Telephone Company
17785 Center Court Drive North
Cerritos, CA 90703
Ph: : (562) 468-6668
Fax: (562) 924-8102
e-mail: vrajan@corporate.lacellular.com
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:48 CDT