Forum Discussion

fomichev's avatar
fomichev
15 years ago

Critical bptm (pid=17858) attempted to write 18 gigabytes, 1666994784 bytes, it is not a multiple of 512

Dear Sirs, We have problems with backup of only one of the clients. Server + Media Server: HARDWARE SOLARIS (SunOS backupserv 5.9 Generic_117171-07 sun4u sparc SUNW,Sun-Fire-V210) VER...
7.1.x and Earlier
Backing Up
Backup and Recovery
NetBackup
  • shans's avatar
    shans
    15 years ago
    HI

    The issues may be with NIC.

    Please find the below Tech Note.

    Exact Error Message
    Attempt to write 8 gigabytes, 1457249836 bytes, it is not a multiple of 512
    media manager - system error occurred (174)

     
    Details:
    Overview:
    During backups, the NetBackup (tm) media server keeps track of the number of bytes received during backup. The media server pads all blocks sent to 512 bytes. After a backup finishes, NetBackup divides the total number of bytes by 512 as an integrity check. If the number does not divide evenly by 512, then it is assumed that some amount of data was not received. A Status 174 error is then seen on Windows clients.   UNIX Clients do not experience the 174 error.

    Troubleshooting:
    Research has shown that this problem is often associated with Network Interface Card (NIC) configuration issues.

    Media Server Log Files:
    The /usr/openv/netbackup/logs/bptm<log.<date> on the Solaris media server will show.
    <32> fill_buffer: attempted to write 58 gigabytes, 1972054444 bytes, it is not a multiple of 512
    <2> mm_child_done: SIGCLD: exit=174, pid=2324
    <2> bptm: EXITING with status 174 <----------

    Resolution:
    Ensure correct configuration of the Network Interface Cards on both the client and media server.

    Windows Client:
    Windows network cards, especially Gigabit Ethernet cards, may drop packets when the NIC is under high load and the driver code is not up to date. These problems have been addressed with updated Windows NIC drivers.
     
    • On the Windows client, click Start | Settings | Control Panel | Hardware | Device Manager | Network Adapter | Properties to determine the NIC vendor and driver version
    • Download and install the latest drivers from the NIC vendor's Web site
    • Additionally, temporarily try breaking any NIC teams that are used if problems persist. This will ensure that the failure isn't a result of the teaming configuration

    Solaris Media Server:
    Ensure that the media server's Gigabit card is not in a 33MHz system slot. It should be in a 66MHz system slot, or an intermittent Status 174 can result.

     
    • Use the Solaris /usr/platform/`arch -k`/sbin/prtdiag -v  command to display the system I/O cards and the slots they reside in
    • Relocate cards as needed. See further details in SUN document ID 41665 at:    http://sunsolve.sun.com
    ·
    Ensure that the Solaris Gigabit driver patch is up to date on the master or media server. The gigabit drivers are separate from the OS patches.
     
    • Run netstat -i to find the Gigabit card type
    • Update as required with the latest available fixes at  http://sunsolve.sun.com
    ·
    http://seer.entsupport.symantec.com/docs/262860.htm
shans's avatar
shans
Level 4
15 years ago
HI

The issues may be with NIC.

Please find the below Tech Note.

Exact Error Message
Attempt to write 8 gigabytes, 1457249836 bytes, it is not a multiple of 512
media manager - system error occurred (174)

 
Details:
Overview:
During backups, the NetBackup (tm) media server keeps track of the number of bytes received during backup. The media server pads all blocks sent to 512 bytes. After a backup finishes, NetBackup divides the total number of bytes by 512 as an integrity check. If the number does not divide evenly by 512, then it is assumed that some amount of data was not received. A Status 174 error is then seen on Windows clients.   UNIX Clients do not experience the 174 error.

Troubleshooting:
Research has shown that this problem is often associated with Network Interface Card (NIC) configuration issues.

Media Server Log Files:
The /usr/openv/netbackup/logs/bptm<log.<date> on the Solaris media server will show.
<32> fill_buffer: attempted to write 58 gigabytes, 1972054444 bytes, it is not a multiple of 512
<2> mm_child_done: SIGCLD: exit=174, pid=2324
<2> bptm: EXITING with status 174 <----------

Resolution:
Ensure correct configuration of the Network Interface Cards on both the client and media server.

Windows Client:
Windows network cards, especially Gigabit Ethernet cards, may drop packets when the NIC is under high load and the driver code is not up to date. These problems have been addressed with updated Windows NIC drivers.
 
  • On the Windows client, click Start | Settings | Control Panel | Hardware | Device Manager | Network Adapter | Properties to determine the NIC vendor and driver version
  • Download and install the latest drivers from the NIC vendor's Web site
  • Additionally, temporarily try breaking any NIC teams that are used if problems persist. This will ensure that the failure isn't a result of the teaming configuration

Solaris Media Server:
Ensure that the media server's Gigabit card is not in a 33MHz system slot. It should be in a 66MHz system slot, or an intermittent Status 174 can result.

 
  • Use the Solaris /usr/platform/`arch -k`/sbin/prtdiag -v  command to display the system I/O cards and the slots they reside in
  • Relocate cards as needed. See further details in SUN document ID 41665 at:    http://sunsolve.sun.com
·
Ensure that the Solaris Gigabit driver patch is up to date on the master or media server. The gigabit drivers are separate from the OS patches.
 
  • Run netstat -i to find the Gigabit card type
  • Update as required with the latest available fixes at  http://sunsolve.sun.com
·
http://seer.entsupport.symantec.com/docs/262860.htm