This one is strange. One of our Win 2008 server with v6.3 client that is getting jbb buffer errors:
==> jbberror.log 07/01/2016 13:35:17 ANS0361I DIAG: ReadFsChangesThread(tid 7340): ReadDirectoryChangesW: Unable to process change notification buffer, the buffer size may be need to be adjusted to avoid this problem in the future. 07/01/2016 13:35:17 ANS0361I DIAG: ReadFsChangesThread(tid 7340): exiting thread. 07/01/2016 13:35:17 ANS0361I DIAG: psFsMonitorThread(tid 6440): Notification buffer overrun for monitored FS 'G:\', journal will be reset. 07/01/2016 13:35:17 ANS0361I DIAG: jnlDbCntrl(): Resetting journal for fs 'G:'. 07/26/2016 10:52:30 ANS0361I DIAG: ReadFsChangesThread(tid 3768): ReadDirectoryChangesW: Unable to process change notification buffer, the buffer size may be need to be adjusted to avoid this problem in the future. 07/26/2016 10:52:30 ANS0361I DIAG: ReadFsChangesThread(tid 3768): exiting thread. 07/26/2016 10:52:30 ANS0361I DIAG: psFsMonitorThread(tid 3776): Notification buffer overrun for monitored FS 'F:\', journal will be reset. 07/26/2016 10:52:30 ANS0361I DIAG: jnlDbCntrl(): Resetting journal for fs 'F:'. In googling we find this article: http://www-01.ibm.com/support/docview.wss?uid=swg21620688 >Even though the "Tivoli Storage Manager (TSM) Journal Based Backup FAQ" >recommends to increase the notification buffer size, it is not applicable in >all cases. >Therefore the recommendation of the Tivoli Storage Manager support is to >adjust the >notification buffer so that the buffer overflow does not occur, increasing or >(in most cases) >DECREASING the notification buffer size. I don't understand decreasing a buffer to prevent an overflow. Any thoughts about this are welcome! Rick ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
