dump0.3 stopped working for one filesystem since april

dump0.3 stopped working for one filesystem since april

Post by Johan Henselman » Sat, 25 May 1996 04:00:00

I have used dump0.3 for xet2fs filesystems since it came out, and I was
very happy with it, as the format is compatible with bsd/sun's dump and

Since april one of the filesystems does not backup anymore:

I get the following message:

/sbin/dump 0bdsfu 32 15000 11000 /dev/nst0 /dev/sda6
  DUMP: Date of this level 0 dump: Fri May 24 17:43:27 1996
  DUMP: Date of last level 0 dump: the epoch
  DUMP: Dumping /dev/sda6 (/usr/local) to /dev/nst0
  DUMP: mapping (Pass I) [regular files]
  DUMP: mapping (Pass II) [directories]
  DUMP: estimated 301164 tape blocks on 0.21 tape(s).
  DUMP: dumping (Pass III) [directories]
  DUMP: master/slave protocol botched.
  DUMP: The ENTIRE dump is aborted.

Does anyone use dump/restore. experienced the same?

As I follow the kernel updates (kernel and libc) I was wondering if
something in april changed that can break a program on one filesystem.

The source of dump is on tsx11-mit.edu, in the ext2fs folder.



Digital priorisXL, pci adaptec 2940 wide/fast (AIC7870)
3c509, 32 MB memory, 2 scsi (1GB IBM DPES-31080), 2.3 GB Quantum VP32210
Creatix ISDN card

GCC 2.72, libc5.3.12, sendmail8.7.5 for the rest mostly slackware3.0
modules 1.3.69(e,f,g,k)



Johan Henselmans

Netsense bv, Nieuwe Herengracht 147 1011 SG Amsterdam

Nieuwe Herengracht 147d 1011 SG Amsterdam