Re: dump restore problem

From: Tomi Vainio - Sun Finland <Tomi.Vainio_at_Sun.COM>
Date: Sun, 27 Apr 2003 01:45:13 +0300
David O'Brien writes:
 > On Sun, Apr 27, 2003 at 12:44:36AM +0300, Tomi Vainio - Sun Finland wrote:
 > > During my ufs2 migration I've used piped dump restore procedure.  Is
 > > it normal that block sizes like 512 or 1000 don't work?  Block size
 > > 512 gives an error and 1000 hangs forever while 126 is working fine.
 > > 
 > > dump 0buf 512 - / | restore xbf 512 -
 > 
 > dump 0abuf 512 - / | restore xf -
 > 
 > Add -a (infinate tape lenght), and let restore figure out the block size.

cat:/mnt/tmp(132)# dump 0abuf 512 - / | restore xf -
  DUMP: WARNING: should use -L when dumping live filesystems!
  DUMP: Date of this level 0 dump: Sun Apr 27 01:44:12 2003
  DUMP: Date of last level 0 dump: the epoch
  DUMP: Dumping /dev/da0s1a (/) to standard output
  DUMP: mapping (Pass I) [regular files]
  DUMP: mapping (Pass II) [directories]
  DUMP: estimated 236472 tape blocks.
  DUMP: dumping (Pass III) [directories]
  DUMP: master/slave protocol botched.
  DUMP: The ENTIRE dump is aborted.
Tape is not a dump tape
Received on Sat Apr 26 2003 - 13:45:18 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:05 UTC