- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: invalid block size
StoreEver Tape Storage
1752794
Members
6448
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-27-2009 11:00 PM
тАО09-27-2009 11:00 PM
invalid block size
Hi.
Has any of you encountered this error while backing up to an MSL6060:
"Tha xMA has detected an error while writing to the device..."
"...the most probable cause is the invalid block size used to configure the backup device."
is there a way to adjust the drives block size? i'm using NSR.
thanks.
Has any of you encountered this error while backing up to an MSL6060:
"Tha xMA has detected an error while writing to the device..."
"...the most probable cause is the invalid block size used to configure the backup device."
is there a way to adjust the drives block size? i'm using NSR.
thanks.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2009 12:21 AM
тАО10-12-2009 12:21 AM
Re: invalid block size
Hi,
I got this from a guide:
At the end of March 2005, Microsoft released Service Pack 1 (SP1) for the Windows Server 2003
platform. With SP1, Microsoft changed the driver tape.sys to allow for NTBackup tapes written on 64-bit
Windows 2003 Server to be read or cataloged on 32-bit Windows 2003 Server systems. The change in
the tape.sys driver imposes a limit on the data transfers to a block size of no greater than 64KB.
Performance issues will be more apparent on all high-performance tape drives such as the HP Ultrium 960
and SDLT 600 using the tape.sys driver.
As a result, backup applications using HP tape drivers (hplto.sys, hpdat.sys, hpdltw32.sys,
hpdltx64.sys, and hpdltw64.sys) and tape.sys driver may experience poor performance and/or
failed backup jobs. If experiencing either of these symptoms, check the backup application with the
software vendor to see if the backup application is using the Microsoft tape driver, tape.sys.
Microsoft released a hotfix that replaces the affected tape.sys file with a version that removes the 64KB
limitation on block sizes; see http://support.microsoft.com/kb/907418/en-us.
This hotfix was integrated
into Windows 2003 Service Pack 2 (SP2).
I got this from a guide:
At the end of March 2005, Microsoft released Service Pack 1 (SP1) for the Windows Server 2003
platform. With SP1, Microsoft changed the driver tape.sys to allow for NTBackup tapes written on 64-bit
Windows 2003 Server to be read or cataloged on 32-bit Windows 2003 Server systems. The change in
the tape.sys driver imposes a limit on the data transfers to a block size of no greater than 64KB.
Performance issues will be more apparent on all high-performance tape drives such as the HP Ultrium 960
and SDLT 600 using the tape.sys driver.
As a result, backup applications using HP tape drivers (hplto.sys, hpdat.sys, hpdltw32.sys,
hpdltx64.sys, and hpdltw64.sys) and tape.sys driver may experience poor performance and/or
failed backup jobs. If experiencing either of these symptoms, check the backup application with the
software vendor to see if the backup application is using the Microsoft tape driver, tape.sys.
Microsoft released a hotfix that replaces the affected tape.sys file with a version that removes the 64KB
limitation on block sizes; see http://support.microsoft.com/kb/907418/en-us.
This hotfix was integrated
into Windows 2003 Service Pack 2 (SP2).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2009 12:23 AM
тАО10-12-2009 12:23 AM
Re: invalid block size
One more possibility:
A potential tape I/O performance issue has been discovered with Windows Server 2003 32-bit systems
configured with Emulex SCSIPort mini-port HBA drivers. This issue only affects those backup applications
using tape block sizes/transfer lengths exceeding 128KB.
Emulex SCSIPort mini-port HBA drivers use a MaximumSGList entry in the Windows registry that defines the maximum data transfer length supported by
the adapter for SCSI commands. Early Emulex drivers, version 5.5.20.8 and older, set this registry entry to
a value of 33 decimal (21 hexadecimal) limiting SCSI transfers to a maximum of 128KB. Beginning with
version 5.5.20.9, this registry entry was increased to 129 decimal (81 hexadecimal) increasing SCSI
transfers to 512KB. The issue surfaces when upgrading an installed Emulex HBA SCSIPort mini-port driver
from driver version 5.5.20.8 and earlier to driver version 5.5.20.10 or later (driver version 5.5.20.9 is
Enterprise Backup Solution design guide 121
exempt from this issue). During the upgrade, the existing MaximumSGList registry entry is not modified
from 33 to 129. Since it remains at the lower value (33), the SCSI transfer length remains at 128K, thus
possibly affecting performance when large block sizes/transfer lengths are used.
To resolve this issue, modify the MaximumSGList in the registry as follows:
CAUTION: Using the Registry Editor incorrectly can cause serious, system-wide problems. Microsoft
cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at
your own risk. Back up the registry before editing.
1. Click Start > Run to open the Run dialog box.
2. Enter regedit to launch the registry editor.
3. Navigate to the following registry key:
\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lpxnds\Parameters\Device\
MaximumSGList
4. Change the REG_DWORD value from 33 to 129.
Hope this helps!
A potential tape I/O performance issue has been discovered with Windows Server 2003 32-bit systems
configured with Emulex SCSIPort mini-port HBA drivers. This issue only affects those backup applications
using tape block sizes/transfer lengths exceeding 128KB.
Emulex SCSIPort mini-port HBA drivers use a MaximumSGList entry in the Windows registry that defines the maximum data transfer length supported by
the adapter for SCSI commands. Early Emulex drivers, version 5.5.20.8 and older, set this registry entry to
a value of 33 decimal (21 hexadecimal) limiting SCSI transfers to a maximum of 128KB. Beginning with
version 5.5.20.9, this registry entry was increased to 129 decimal (81 hexadecimal) increasing SCSI
transfers to 512KB. The issue surfaces when upgrading an installed Emulex HBA SCSIPort mini-port driver
from driver version 5.5.20.8 and earlier to driver version 5.5.20.10 or later (driver version 5.5.20.9 is
Enterprise Backup Solution design guide 121
exempt from this issue). During the upgrade, the existing MaximumSGList registry entry is not modified
from 33 to 129. Since it remains at the lower value (33), the SCSI transfer length remains at 128K, thus
possibly affecting performance when large block sizes/transfer lengths are used.
To resolve this issue, modify the MaximumSGList in the registry as follows:
CAUTION: Using the Registry Editor incorrectly can cause serious, system-wide problems. Microsoft
cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at
your own risk. Back up the registry before editing.
1. Click Start > Run to open the Run dialog box.
2. Enter regedit to launch the registry editor.
3. Navigate to the following registry key:
\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lpxnds\Parameters\Device\
MaximumSGList
4. Change the REG_DWORD value from 33 to 129.
Hope this helps!
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP