search for: highestcommitedusn

Displaying 4 results from an estimated 4 matches for "highestcommitedusn".

2018 Jan 30
0
[Patches] for dbcheck (Re: [Patches] AD Database corruption after upgrade from <= 4.6 to 4.7 (bug #13228))
...#39; modification (which typically never changes and therefor matches the object creation time). We also use version = 0 in order to match the link creation of 4.7 and older releases. This way we can easily identify recreated forward links and we avoid a new meta data stamp and incrementing of the highestCommitedUSN. So each affected dc will just recover the value in the local database. And any incoming replication should overwrite the value again. See also https://bugzilla.samba.org/show_bug.cgi?id=13228 metze Am 22.01.2018 um 10:49 schrieb Stefan Metzmacher via samba-technical: > Hi, > > here...
2018 Jan 22
6
[Patches] AD Database corruption after upgrade from <= 4.6 to 4.7 (bug #13228)
Hi, here're patches to avoid a database corruption with linked attributes, e.g. member/memberOf. See https://bugzilla.samba.org/show_bug.cgi?id=13228 As a temporary solution admins can add "server services = -kcc" to the global section of smb.conf. Also DO NOT repair the following errors with samba-tool dbcheck! "Remove duplicate links in attribute" and "ERROR:
2018 Jan 31
2
[Patches] for dbcheck (Re: [Patches] AD Database corruption after upgrade from <= 4.6 to 4.7 (bug #13228))
...cally never changes and therefor > matches the object creation time). We also use version = 0 > in order to match the link creation of 4.7 and older releases. > > This way we can easily identify recreated forward links > and we avoid a new meta data stamp and incrementing of > the highestCommitedUSN. So each affected dc will just recover > the value in the local database. And any incoming > replication should overwrite the value again. > > See also https://bugzilla.samba.org/show_bug.cgi?id=13228 > > metze > > Am 22.01.2018 um 10:49 schrieb Stefan Metzmacher via samba-t...
2018 Jan 31
0
[Patches] for dbcheck (Re: [Patches] AD Database corruption after upgrade from <= 4.6 to 4.7 (bug #13228))
...therefor >> matches the object creation time). We also use version = 0 >> in order to match the link creation of 4.7 and older releases. >> >> This way we can easily identify recreated forward links >> and we avoid a new meta data stamp and incrementing of >> the highestCommitedUSN. So each affected dc will just recover >> the value in the local database. And any incoming >> replication should overwrite the value again. >> >> See also https://bugzilla.samba.org/show_bug.cgi?id=13228 >> >> metze >> >> Am 22.01.2018 um 10:49 schri...