From owner-freebsd-questions Wed Nov 27 02:38:10 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA10375 for questions-outgoing; Wed, 27 Nov 1996 02:38:10 -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 CAA10370 for ; Wed, 27 Nov 1996 02:38:05 -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); Wed, 27 Nov 1996 10:41:30 +0000 Message-ID: <329C1996.25BD@nation-net.com> Date: Wed, 27 Nov 1996 10:36:06 +0000 From: Paul Walsh Organization: NATION-NET X-Mailer: Mozilla 2.0 (Win95; I) MIME-Version: 1.0 To: FreeBSD 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] Any ideas anyone? Is there a way perhaps of exluding the bad sectors/badsect files from the dump? Regards, Paul Walsh.