Thanks to everyone who responded and very special thanks to Waqar Hafiz
(whafiz@london.micrognosis.com) who pointed me to the right direction.
My original question was:
> I ran into some strange dump problems after upgrading our 670MP from
> 4.1.3 to 5.5.1. Ufsdump does not work at all on two disks (both
> Micropolis 1936-21 2.8 GB). When I try to dump them (unmounted, fscked)
> I get errors like:
>
> DUMP: Warning - cannot read sector 3896516166 of `/dev/rdsk/c1t1d0s6'
> DUMP: bread: DEV_LSEEK2 error
> DUMP: Warning - cannot read sector 3896516167 of `/dev/rdsk/c1t1d0s6'
> DUMP: bread: DEV_LSEEK2 error
> DUMP: Warning - cannot read sector 3896516168 of `/dev/rdsk/c1t1d0s6'
>
> After 32 errors dump stops. I tried also to make a new filesystem on
> one partition, but the problem didn't go way. Strange thing is that
> when I run ufsdump under truss, like 'truss -f -o /dev/null ufsdump 0f
> /mnt/testdump /dev/rdsk/c1t1d0s6' it works!
>
The solution was to disable tagged command queueing on the SCSI bus. I
put this line to /etc/system and the problem disappeared:
set scsi_options & ~0x80
Sun managers summary on 14.10.1995, 'block read errors from ufsdump'
described the same situation and the solution.
Tuomo Salmela
-------------------------------------------------------------------------------
Tuomo Salmela Tel: +358 3 316 3631
VTT Automation / Machine automation Fax: +358 3 316 3694
P.O. Box 13021, FIN-33101 Tampere Finland
-------------------------------------------------------------------------------
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:16 CDT