Tape Device Block issue on Storage Node

[DaiHawkins]

NW 7.2.1, on Win Serv2003

I am running with a master Server and 1 Storage Node

In the library are 4 drives, which al have multipath set up so the Storag eNod ecan write to them directly on the SAN.

They have been working okay for a number of months but now when I try to do anything with Tape 3 on the storage node it gives a read or verify error. If I use the same device but use the master server path i.e \\.\Tape3 nor dr=client:\\Tape3 then it works okay.

I have run jbverify, which works for all the drives apart from tape 3 useing the SNode path.
The output table at the end shows that this tape drive has Blocks N/A where the rest have a vaule of 6536.

Any Ideas ?

 

[605]

I guess that the storage node rebooted and the device numbering changed at this point in time. The easiest way most likely is to delete and reinstall the jukebox resource.

 

[DaiHawkins]

I have checked the device numbering as i ran into this problem when first setting up the library and drives, all that is okay.

Is there anyway to force the Blocks on a drive ? I have already removed the rd=client:\\.\Tape 3 device and readded it.

 

[605]

By default, Windows blocks are 64kB max. As both of your hosts are Windows, i do not expect problems until you receive a tape which has been written by a UNIX node.

I do not think it is a block size problem because you said that the drives can not read the label. Labels are always written with 32kB.

 

[DaiHawkins]

On going through and checking things again, it turns out after i removed the rd device, when i re added it I had a type error, all works okya now i have corrected it. although not sure what caused the issue in the first place.