From owner-freebsd-hackers Mon Jul 8 5:11:37 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC67837B400 for ; Mon, 8 Jul 2002 05:11:34 -0700 (PDT) Received: from mobile.webweaving.org (fia224-72.dsl.hccnet.nl [62.251.72.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D1E543E31 for ; Mon, 8 Jul 2002 05:11:33 -0700 (PDT) (envelope-from dirkx@covalent.net) Received: from localhost.leiden.webweaving.org (localhost.leiden.webweaving.org [127.0.0.1] (may be forged)) by mobile.webweaving.org (8.12.2/8.10.2) with ESMTP id g68CADM4000674 for ; Mon, 8 Jul 2002 14:10:13 +0200 (CEST) X-Curiosity: Killed the Cat X-Huis-aan-Huis-deur-sticker: nee-nee X-Spam: no X-Passed: MX on Gandalf.WebWeaving.org Mon, 8 Jul 2002 14:10:13 +0200 (CEST) and masked X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Date: Mon, 8 Jul 2002 14:10:13 +0200 (CEST) From: dirkx@covalent.net X-X-Sender: dirkx@mobile.webweaving.org To: freebsd-hackers@FreeBSD.ORG Subject: Re: FSCK/current and dump errors In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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 dirkx@covalent.net 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 majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message