Hi Rodney, We're actually somewhat "cold" towards this as a recovery step these days. As of 2k SP3, we disabled this by default.
We're far more "warm" to recovering the node by hand and increasing the journal size so you don't hit this again (if you need the larger journal size). The increasing of journal size is only if you really need it. If this is a one-off problem, I'd rather set up monitoring (Ultrasound) and catch it before we wrap again. Note that if you do need to do a D2, you will vvJoin the replica set. A few articles that might help understand what I'm talking about. :) http://support.microsoft.com/kb/292438 http://support.microsoft.com/default.aspx?scid=kb;EN-US;290762 It's hard to make a recommendation with the data given so far (I'd need full FRS logs) but I smell a D2 coming. That's just a hunch though. ~Eric -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rodney Gardiner Sent: Sunday, October 24, 2004 11:13 PM To: [EMAIL PROTECTED] Subject: [ActiveDir] JRNL_WRAP_ERROR in File Replication Service Event LOG Yet another problem.... I have seen this before and tried to do what the message states at the bottom about changing "Enable Journal Wrap Automatic Restore" registry parameter to 1. I did this once before and had major problems. Is this anything to be concerned about and how would I go about fixing it? The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR. Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" Replica root path is : "c:\winnt\sysvol\domain" Replica root volume is : "\\.\C:" A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons. [1] Volume "\\.\C:" has been formatted. [2] The NTFS USN journal on volume "\\.\C:" has been deleted. [3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal. [4] File Replication Service was not running on this computer for a long time. [5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:". Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state. [1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service. [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set. WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again. To change this registry parameter, run regedit. Click on Start, Run and type regedit. Expand HKEY_LOCAL_MACHINE. Click down the key path: "System\CurrentControlSet\Services\NtFrs\Parameters" Double click on the value name "Enable Journal Wrap Automatic Restore" and update the value. If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above. Rodney List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
