From owner-freebsd-questions  Mon Mar 27 11:31:24 1995
Return-Path: questions-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA00857 for questions-outgoing; Mon, 27 Mar 1995 11:31:24 -0800
Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA00834 for <freebsd-questions@FreeBSD.org>; Mon, 27 Mar 1995 11:31:12 -0800
Received: by gvr.win.tue.nl (8.6.10/1.53)
    id TAA04576; Mon, 27 Mar 1995 19:22:59 +0200
From: guido@gvr.win.tue.nl (Guido van Rooij)
Message-Id: <199503271722.TAA04576@gvr.win.tue.nl>
Subject: Re: question about dump
To: bob@obiwan.pmr.com (Bob Willcox)
Date: Mon, 27 Mar 1995 19:22:58 +0200 (MET DST)
Cc: guido@IAEhv.nl, freebsd-questions@FreeBSD.org
In-Reply-To: <m0rtGE8-00030iC@obiwan.pmr.com> from "Bob Willcox" at Mar 27, 95 08:57:08 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 1306      
Sender: questions-owner@FreeBSD.org
Precedence: bulk

Bob Willcox wrote:
> 
> Guido van Rooij wrote:
> > 
> > What happens when I do a level 0 dump on a system that is not in single
> > user mode? More specifically: if files/directories get deleted after
> > dump has made ist dump table?
> 
> This is a good question.  I do this all the time, but don't really understand
> the consequences of doing so.  (I find it too painful to take my system down
> to single user mode for the appx. 6 hrs it takes to do the full dump :-()

The reason I am asking is becasue we get complaints from dump all the time,
like:

      DUMP: read error from /dev/rsd1h: Invalid argument: [block -1444115938]: count=8192
      DUMP: bread: lseek2 fails!
      DUMP: read error from /dev/rsd1h: Invalid argument: [sector -1444115938]: count=512
    ...]
    bread: lseek fails
      DUMP:   DUMP:   DUMP: bread: lseek fails
    read error from /dev/rsd1h: Invalid argument: [sector -126001564]: count=512
    bread: lseek fails

and this repeated all the time.

We also see empty messages from the scsi subsystem around the backup time.
That might also explain some things:

Mar 27 07:53:26 iaehv kernel: sd1(ncr0:1:0): 
Mar 27 07:53:27 iaehv kernel: sd1(ncr0:1:0): sd1(ncr0:1:0): sd1(ncr0:1:0): sd1(ncr0:1:0): sd1(ncr0:1:0): 
Mar 27 07:56:43 iaehv kernel: sd0(ncr0:0:0): 

-Guido