From owner-freebsd-questions  Thu Nov 28 05:12:21 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id FAA25101
          for questions-outgoing; Thu, 28 Nov 1996 05:12:21 -0800 (PST)
Received: from www.nation-net.com (www.nation-net.com [194.159.125.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA25096
          for <questions@freebsd.org>; Thu, 28 Nov 1996 05:12:18 -0800 (PST)
Received: from mag.nation-net.com (194.159.125.14) by www.nation-net.com
 with SMTP (Apple Internet Mail Server 1.0); Thu, 28 Nov 1996 13:15:45 +0000
Message-ID: <329D8F3B.49A9@nation-net.com>
Date: Thu, 28 Nov 1996 13:10:19 +0000
From: Stephen Walsh <steve@nation-net.com>
Organization: NATION-NET
X-Mailer: Mozilla 2.0 (Win95; I)
MIME-Version: 1.0
To: questions@freebsd.org
Subject: dump/restore cw. bad blocks
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Since getting a bad block and isolating it with badsect I am having
trouble with dump/restore on that file system.

After a full dump on /usr (which included a console message about the
bad block), I tried a restore tf with the following result:

>Level 0 dump of /usr on www.walshsimmons.co.uk:/dev/wd0f
>Label: none
>Checksum error 244737, inode 0 file (null)
>no header after volume mark!
>abort? [yn]
>dump core? [yn]

Is there a way perhaps of exluding the bad sectors/badsect files from 
the dump, maybe the "nodump" flag mentioned in man?

Regards, Paul Walsh.