From owner-freebsd-questions  Mon Apr  3 10:04:44 1995
Return-Path: questions-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA12931 for questions-outgoing; Mon, 3 Apr 1995 10:04:44 -0700
Received: from grendel.csc.smith.edu (grendel.csc.smith.edu [131.229.222.23]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA12925 for <freebsd-questions@FreeBSD.org>; Mon, 3 Apr 1995 10:04:42 -0700
Received: from localhost (jfieber@localhost) by grendel.csc.smith.edu (8.6.5/8.6.5) id NAA02177; Mon, 3 Apr 1995 13:04:42 -0400
From: jfieber@cs.smith.edu (John Fieber)
Message-Id: <199504031704.NAA02177@grendel.csc.smith.edu>
Subject: Re: HELP:backups failing. dump broken?
To: guido@IAEhv.nl (Guido van Rooij)
Date: Mon, 3 Apr 1995 13:04:42 -0400 (EDT)
Cc: freebsd-questions@FreeBSD.org
In-Reply-To: <199504011944.VAA29080@iaehv.IAEhv.nl> from "Guido van Rooij" at Apr 1, 95 09:44:49 pm
Content-Type: text
Content-Length: 703       
Sender: questions-owner@FreeBSD.org
Precedence: bulk

Guido van Rooij writes:
> I cant seem to find any reason for dump(8) to fail. Yet it does.
> We have a system that runs perfectly. However, when dumping (level 0)
> filesystems, we sometimes get strange errors with dump.

[...]

>   DUMP: bread: lseek2 fails!
>   DUMP: read error from /dev/rsd1h: Invalid argument: [sector -814171466]: count=512

I had this problem after upgrading to 2.0 when backing up a
filesystem created under 1.1.  The solution was to unmount the
filesystem in question, and fsck -c 3.  Read the fsck man page
for details.

-john

=== jfieber@cs.smith.edu ================================================
=================================== Come up and be a kite!  --K. Bush ===