FYI: The error described below is fully fixed by moving from 1.10.2.4 to rev. 1.22 of traverse.c. It is the change from 1.21 -> 1.22 which restores the ability to do a backup again.
Thanks! Dw. On Sat, 29 Jun 2002 [EMAIL PROTECTED] wrote: > Not sure if I should blame current - but see the errors below. I've tried > an fsck and an fsck -f from single user mode on each of the affected disks > (7 disk, mix of ide/scsi give this). > > FSCK comes through clean. Prior to running -CURRENT the disks where > attached to a 2.0.8 machine; and the dump prior to the upgrade is good > (and restore can fully read it). > > But right now a real dump to tape; or a dump to /dev/null give me the > errors below. > > -> Is there a more throurough consistency check I could do ? > > I've attached one of the SCSU disks to a 4.5 RELEASE machine; and fsck > sees no errors; and there dump gives me similar errors. > > Any ideas, or should I just ignore this as -CURRENT madness :-) > > Thanks, > > Dw > > sendbackup: info BACKUP=/sbin/dump > sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/sbin/restore -f... - > sendbackup: info COMPRESS_SUFFIX=.gz > sendbackup: info end > | DUMP: Date of this level 0 dump: Sat Jun 29 05:10:43 2002 > | DUMP: Date of last level 0 dump: the epoch > | DUMP: Dumping /dev/ad2s1f (/local2) to standard output > | DUMP: mapping (Pass I) [regular files] > | DUMP: mapping (Pass II) [directories] > | DUMP: estimated 1874624 tape blocks. > | DUMP: dumping (Pass III) [directories] > | DUMP: dumping (Pass IV) [regular files] > ? DUMP: read error from /dev/ad2s1f: Invalid argument: [block -645840818]: count=-1 > ? DUMP: read error from /dev/ad2s1f: Invalid argument: [sector -645840818]: >count=-1 > ? DUMP: read error from /dev/ad2s1f: Invalid argument: [sector -645840817]: >count=-1 > ? DUMP: read error from /dev/ad2s1f: Invalid argument: [sector -645840816]: >count=-1 > ...cut 150 lines... > ? DUMP: read error from /dev/ad2s1f: Invalid argument: [sector -645840749]: >count=-1 > ? DUMP: read error from /dev/ad2s1f: Invalid argument: [sector -645840748]: >count=-1 > ? DUMP: read error from /dev/ad2s1f: Invalid argument: [sector -645840747]: >count=-1 > ? DUMP: read error from /dev/ad2s1f: Invalid argument: [block -645840746]: count=-1 > ? DUMP: read error from /dev/ad2s1f: Invalid argument: [sector -645840746]: >count=-1 > ...cut 1500 lines... > > ? DUMP: read error from /dev/ad2s1f: Invalid argument: [sector -645840147]: >count=-1 > ? DUMP: More than 32 block read errors from 135025408 > ? DUMP: This is an unrecoverable error. > ? DUMP: fopen on /dev/tty fails: Device not configured > | DUMP: The ENTIRE dump is aborted. > sendbackup: error [/sbin/dump returned 3] > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
