Re: [Dump-users] RE: Dump HOWTO

[Bernhard E. <be...@be...>]

Stelian Pop wrote:
[...]
> Wouldn't that be that, for some reason, your DDS-2 drive is configured
> for only a fixed blocksize of 32k ?

No, it's default is variable blocksize:
# mt status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 0 bytes. Density code 0x13 (DDS (61000 bpi)).
Soft error count since last status=0
General status bits on (41010000):
 BOT ONLINE IM_REP_EN

> Dump, by default, uses a 10k blocksize.

The default blocksize of dump isn't mentioned in the man page.

> Try to run a /sbin/dump 0ab 32 /tmp/. Maybe it helps...

I already tried it, didn't help then, if I remember correctly. Now it
works. ??

Dump with "-b 32" works well, thanks for the hint. Seems to eliminate
the need for "| dd obs=32k of=$TAPE".

> Or add try a /sbin/restore rdv (debug and verbose enabled).

Tape written with "dump 0a /tmp":

# /sbin/restore rvd
Verify tape and initialize maps
Tape block size is 32
Volume header (old inode format) 
Dump   date: Tue Jun 27 10:24:36 2000
Dumped from: the epoch
Level 0 dump of /tmp on ente:/dev/hdb11
Label: none
maxino = 57345
Used inodes map header
Dumped inodes map header
Begin level 0 restore
Initialize symbol table.
Extract directories from tape
File header, ino 46305
File header, ino 46306
File header, ino 46307
File header, ino 46315
File header, ino 46317
. is not on the tape
Root directory is not on tape
abort? [yn] y
dump core? [yn] n

I wonder why restore says "Tape block size is 32". You told me, dump
used 10k blocks and the tape drive is set to variable blocksize. So why
32KB blocks?

Let's have a try:
# /sbin/restore rb 10

With "-b 10", restore works well reading a tape witten by "dump 0a
/tmp". Maybe a bug in restore to figure out the tape's blocksize?