All, I just made the cut-over from a SCSI-attached L180 (4 x SDLT320) library connected to a Solaris 8 host, to a FC-attached L500 (4 x LTO3) into 2 x T2000 hosts. I now want to continue using my L18
Ty, I think you are on the right track looking at block sizing. Here are some ideas of where to look, but if it ends up you need to have different block sizes on different devices, I don't know how t
Author: Fazil Saiyed <fazil.saiyed AT ANIXTER DOT COM>
Date: Fri, 19 May 2006 09:20:29 -0400
Looks like when you moved from SCSI to FC drives, your privious Block size on the drive was lower ( or heigher) then now, this would be a problem, check and see if you could lower the block size on o
Thanks Fazil for your input. I'm inclined to agree with you but I'm confused by the fact that scanner -v is showing the block size as 131072, or 128K. -ty Phillip T. ("Ty") Young, DMA Manager, Data C
Author: Davina Treiber <DavinaTreiber AT PEEVRO.CO DOT UK>
Date: Fri, 19 May 2006 15:44:00 +0100
Ty, In this case the reference to block size is almost certainly a red herring. The message quotes 32768, well that wouldn't have been the block size used on your previous drives anyway. You are basi
I can verify Davina's claim: we have SDLT600s and get "Block size is 65538 bytes not 131072 bytes" msgs, but we do not have problems with restores. steve - - - systems & network manager high energy p
Author: Fazil Saiyed <fazil.saiyed AT ANIXTER DOT COM>
Date: Mon, 22 May 2006 08:56:34 -0400
One thing i would question is if the currently written Tapes with existing block sizes is being read\restored correctly without errors, then there is no reason to doubt that FC setup\errors, this err