Forum Discussion

Amaan's avatar
Amaan
Level 6
13 years ago

Tape loading error

Master server 7.0.1/ Windows 2008 R2

Media server 7.0.1/ Windows 2003

Tape drive LTO2/tape LTO2

Couple days before i have made some tuning and changed BUFFER size to 262144 from 65536. After that i started getting below error:


1/23/2012 9:25:40 AM - started process bptm (3552)
1/23/2012 9:25:40 AM - mounting 213087
1/23/2012 9:25:40 AM - granted resource 213087
1/23/2012 9:25:40 AM - granted resource CERTANCE.ULTRIUM2.000
1/23/2012 9:25:40 AM - granted resource daaa-hcart2-robot-tld-3
1/23/2012 9:27:12 AM - Error bptm(pid=3552) The tape device at index -1 has a maximum block size of 65536 bytes, a buffer size of 262144 cannot be used
1/23/2012 9:27:12 AM - Warning bptm(pid=3552) media id 213087 load operation reported an error    
1/23/2012 9:27:12 AM - current media 213087 complete, requesting next resource Any
1/23/2012 9:28:41 AM - granted resource 213087
1/23/2012 9:28:41 AM - granted resource CERTANCE.ULTRIUM2.000
1/23/2012 9:28:41 AM - granted resource daaa-hcart2-robot-tld-3
1/23/2012 9:28:42 AM - started process bptm (3552)
1/23/2012 9:28:42 AM - mounting 213087
1/23/2012 9:30:13 AM - Error bptm(pid=3552) The tape device at index -1 has a maximum block size of 65536 bytes, a buffer size of 262144 cannot be used
1/23/2012 9:30:13 AM - Warning bptm(pid=3552) media id 213087 load operation reported an error    
1/23/2012 9:30:13 AM - current media 213087 complete, requesting next resource Any

 

I am not sure if  I am getting this for all tapes. Because i found that some of the tapes have been written after the changes. What can be reason fo this error.

Thanks!

  • "The tape device at index -1 has a maximum block size of 65536 bytes, a buffer size of 262144 cannot be used"

    NBU is merely REPORTING the error.

    I have seen this some time ago when the default Windows 2003 tape driver was used. It is also possible that the HBA is limiting block size.

    Have a look at this TN: http://www.symantec.com/docs/TECH78069

5 Replies

  • I am not sure how good LTO2 is at handling that buffer size

    LTO4 and above runs best with that size.

    It may also be due to the header already on the tape which knows which block size has been use previosuly - generally if it detects a 65536 header it will just use that size so old tapes would not error as they would ignore your setting until then had been re-labelled but any new tapes would try and use it and perhaps fail

    For LTO2 I would stick with the default of 65536

  • "The tape device at index -1 has a maximum block size of 65536 bytes, a buffer size of 262144 cannot be used"

    NBU is merely REPORTING the error.

    I have seen this some time ago when the default Windows 2003 tape driver was used. It is also possible that the HBA is limiting block size.

    Have a look at this TN: http://www.symantec.com/docs/TECH78069

  • I have see Emulex cards to cut the block sizes from 256 to 4x64, I will update the hba firmware just to be sure and also the tape drive firmware, run a dd test to remove netbackup from the ecuation, also use a different media server to see if something going on in that box.

  • Didnt research root cause of the issue. just changed the value back into 65536. will try to work on this later. will put the root cause of the issue and solution. will go through all above advices.

  • I'm with Maianne on this - I think NBU is reporting the issue, but is not the cause.  Ok, I accept the blocksize change 'starts' the problem, but I suspect that it is the HBA that is the root cause.

    Martin