Hi,

We have set up journaling on a Windows 2012 file server with approximately
5 million files.  They files don't change very often and the turnover is
small.  We are receiving the following error:

02/25/2017 16:52:33 ANS0361I DIAG: ReadFsChangesThread(tid 3264):
ReadDirectoryChangesW: Unable to process change notification buffer,  the
buffer size may be need to be adjusted to avoid this problem in the
future.
02/25/2017 16:52:33 ANS0361I DIAG: ReadFsChangesThread(tid 3264): exiting
thread.
02/25/2017 16:58:26 ANS0361I DIAG: psFsMonitorThread(tid 3616):
Notification buffer overrun for monitored FS 'G:\', journal will be reset.
02/25/2017 16:58:26 ANS0361I DIAG: jnlDbCntrl(): Resetting journal for fs
'G:'.

After reading the articles (there are not many) regarding journal buffer
over runs, we have changed the parameters as indicated in the IBM article
(http://www-01.ibm.com/support/docview.wss?uid=swg21620688) to the
following in the jbb.ini file:


; Notification Buffer Size - default 32 Kbytes for files, 16 Kbytes for
dirs
;
NotifyBufferSize=0x00001000
DirNotifyBufferSize=0x00001000
JournaledFileSystems=G:\
;

The error is still occurring.  We use journaling on several other servers
without issue.  Does anyone have an idea on what adjustments can be made
to alleviate this?  We are running version 7.1.6.2 of the client.

Thanks,
Mike