Ranveer Attalia wrote:
Was wonderig if someone could help. I got a failure on one of my
partitions yesterday night complaining about the error in the subject
heading. I thought it may be a problem with the actual partition on the
server Telsun4 (see info. below).
Therefore I umounted the /ccmbackup partition and then fsck'd it and it
was fine.
Any ideas would be helpful
[...]
FAILURE AND STRANGE DUMP SUMMARY:
telsun4 /ccmbackup lev 0 FAILED [/usr/sbin/ufsdump returned 3]
[...]
FAILED AND STRANGE DUMP DETAILS:
/-- telsun4 /ccmbackup lev 0 FAILED [/usr/sbin/ufsdump returned 3]
sendbackup: start [telsun4:/ccmbackup level 0]
sendbackup: info BACKUP=/usr/sbin/ufsdump
sendbackup: info RECOVER_CMD=/usr/sbin/ufsrestore -f... -
sendbackup: info end
| DUMP: Writing 32 Kilobyte records
| DUMP: Date of this level 0 dump: Thu Nov 11 22:45:54 2004
| DUMP: Date of last level 0 dump: the epoch
| DUMP: Dumping /dev/rdsk/c2t2d0s3 (telsun4:/ccmbackup) to standard
output.
| DUMP: Mapping (Pass I) [regular files]
| DUMP: Mapping (Pass II) [directories]
| DUMP: Estimated 6087156 blocks (2972.24MB) on 0.04 tapes.
| DUMP: Dumping (Pass III) [directories]
| DUMP: Dumping (Pass IV) [regular files]
| DUMP: 34.18% done, finished in 0:19
| DUMP: 61.35% done, finished in 0:12
| DUMP: Warning - block 223391968 is beyond the end of
`/dev/rdsk/c2t2d0s3'
? DUMP: bread: dev_seek error: Error 0
[...]
? DUMP: More than 32 block read errors from dump device
`/dev/rdsk/c2t2d0s3'
| DUMP: NEEDS ATTENTION: Do you want to attempt to continue? ("yes" or
"no") DUMP: The ENTIRE dump is aborted.
sendbackup: error [/usr/sbin/ufsdump returned 3]
The seek errors are probably a result of an active filesystem.
When you unmounted it, and fsck-ed, it was fine again.
If it happens only now and then, don't worry. Try to not run
any programs that do heavy input/output during the backup, if
possible.
If it happens frequently, use snapshots, if your OS permits it,
to freeze a filesystem in a few seconds, and make a backup of
that snapshot.
Or use gnutar instead of ufsdump, which, at least, manages to make
a consistent backup of everything that did not change -- files that
did change *may* be inconsistent, and gnutar warns which ones (logfiles
that are only appended, are nevertheless consistent).
--
Paul Bijnens, Xplanation Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************
|
