It definitely sounds like a block-mismatch issue.  If you mount a volume on
each of the 3 platforms, you should be able to see what block size they're
using from the Volume details in Device info of nwadmin.
I noticed in 7.x that there's now a field (in the Config tab of Device
config on Windows nwadmin) where block size can apparently be set.  By
default it is set to "Handler default".  (I don't recall seeing this in
6.x, but maybe it crept into 6.1.4??)
Other than that, you'll have to look up setting the
NSR_DEV_BLOCK_SIZE_drivetype parameter (see Admin guide), or messing with
stinit.def or somesuch config item.

hth, cf

On Fri, 13 Aug 2004 10:49:19 -0400, Rich Graves <rcgraves AT BRANDEIS DOT EDU>
wrote:

>We have a backup SAN with 2 NetApps, 2 Suns, and 1 Linux dedicated storage
>node (licensed to back up only itself) sharing 7 AIT-3 drives, 3 of which
>are enabled for Dynamic Drive Sharing. The Suns are configured
>
>  SONY_AIT   =   1,0x36,0,0xd639,4,0x00,0x00,0x00,0x00,0;
>
>which I think means that they will use full 64K block size (Sun's default
>behavior is 64K - 1).
>
>The NetApps are at the defaults.
>
>The NetApps and Suns have interoperated happily for years.
>
>I'm not sure we've pinned it down, but I think the Suns and NetApps are
>having intermittent problems reading tapes originally labeled on the Linux
>box, and vice versa.
>

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=