Apparently /usr/sbin/rdump in V5.1, pk4 (BL18) cannot write to a remote
tape. I can write to other remote devices, eg /dev/null.
Restoring the pre-pk4 rdump cures the problem
-olle eriksson
On Thu, 6 Dec 2001, Olle Eriksson wrote:
>
> When issuing the following command from a V5.1 pk3 to a V5.1 pk4
> system, rdump aborts with a SIGSEV. This did not occur before
> installing pk4. Any idea about this?
>
> command:
>
> rsh xx.xx.xx.xx -l root /usr/sbin/rdump 0ubf 64
> yyy:/dev/ntape/tape0_d1 /usr/data >>&! /var/spool/mqueue/satdata
>
>
> The log:
>
> rdump: Dumping from host xx.xx.xx.xx
> rdump: Date of this level 0 dump: Thu Dec 6 09:31:24 2001 MET
> rdump: Date of last level 0 dump: the start of the epoch
> rdump: Dumping /dev/rdisk/dsk1h (/usr/data) to /dev/ntape/tape0_d1 on host yyy
> rdump: Mapping (Pass I) [regular files]
> rdump: Mapping (Pass II) [directories]
> rdump: SIGSEGV received -- ABORTING!
> rdump: Child 8070 returns low-byte status 206
>
> -olle eriksson
>
>
>
>
Received on Thu Dec 13 2001 - 12:13:39 NZDT