Displaying 5 results from an estimated 5 matches for "changetim".
Did you mean:
changetime
2012 May 09
6
"file not found" under high-contention
Hello,
For several years I've been experiencing
an intermittent Samba error when running
a very intense, highly parallel build/compile
jobset.
A file is reported as "not found" even though
it most certainly exists and re-running the
compile jobset always succeeds.
Samba version is 3.6.4 running on CentOS 5.8
with 64-bit kernel 2.6.18-308.4.1.el5. Windows
side is 64-bit Window
2018 Jan 30
0
[Patches] for dbcheck (Re: [Patches] AD Database corruption after upgrade from <= 4.6 to 4.7 (bug #13228))
...reviewed for master, we'll also release
a new upstream 4.7 release with the fixes included.
More technical details:
As we lost the replication meta data for the forward link,
we create them using a special invocationId
ffffffff-4700-4700-4700-000000b13228 and an originating_usn
of 1. The add/changetime/local_usn are the one from the last
'objectClass' 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...
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))
...elease
> a new upstream 4.7 release with the fixes included.
>
> More technical details:
>
> As we lost the replication meta data for the forward link,
> we create them using a special invocationId
> ffffffff-4700-4700-4700-000000b13228 and an originating_usn
> of 1. The add/changetime/local_usn are the one from the last
> 'objectClass' 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 recr...
2018 Jan 31
0
[Patches] for dbcheck (Re: [Patches] AD Database corruption after upgrade from <= 4.6 to 4.7 (bug #13228))
....7 release with the fixes included.
>>
>> More technical details:
>>
>> As we lost the replication meta data for the forward link,
>> we create them using a special invocationId
>> ffffffff-4700-4700-4700-000000b13228 and an originating_usn
>> of 1. The add/changetime/local_usn are the one from the last
>> 'objectClass' 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...