search for: 93db

...alled DC2 which for the moment holds all the FSMO roles. The whole replacing an ad dc with another one worked out great but when I run the command samba-tool dbcheck --cross-ncs on DC2 I got 3 "NOTES" and 2 "WARNING" stating (the DN has been obscured and "513a2ea7-9ad8-496f-93db-2532cc6e9c45" was the GUID of DC1): Checking 4694 objects NOTE: old (due to rename or delete) DN string component for lastKnownParent in object CN=NTDS Settings\0ADEL:513a2ea7-9ad8-496f-93db-2532cc6e9c45,CN=DC1\0ADEL:3ccd9bf3-e19a-49d9-a1a1-6afe151b72b3,CN=Servers,CN=Default-First-Site-Name,CN...

...alled DC2 which for the moment holds all the FSMO roles. The whole replacing an ad dc with another one worked out great but when I run the command samba-tool dbcheck --cross-ncs on DC2 I got 3 "NOTES" and 2 "WARNING" stating (the DN has been obscured and "513a2ea7-9ad8-496f-93db-2532cc6e9c45" was the GUID of DC1): > Checking 4694 objects > NOTE: old (due to rename or delete) DN string component for lastKnownParent in object CN=NTDS Settings\0ADEL:513a2ea7-9ad8-496f-93db-2532cc6e9c45,CN=DC1\0ADEL:3ccd9bf3-e19a-49d9-a1a1-6afe151b72b3,CN=Servers,CN=Default-First-Si...

I was wondering if anyone would be able to shed some light on how a file could end up with inconsistent md5sums on Gluster backend storage. Our configuration is running on Gluster v3.1.5 in a distribute-replicate setup consisting of 8 bricks. Our OS is Red Hat 5.6 x86_64. Backend storage is an ext3 RAID 5. The 8 bricks are in RR DNS and are mounted for reading/writing via NFS automounts.

.... 0x0010 010a 0000 0000 0000 c0a8 0101 0000 0000 ................ 0x0020 0000 0000 0000 0000 0000 0000 0000 068b ................ 0x0030 77c8 w. 10:42:50.321402 arp reply 192.168.1.1 is-at 0:3:93:db:7c:6 0x0000 0001 0800 0604 0002 0003 93db 7c06 c0a8 ............|... 0x0010 0101 0002 3fab 183f c0a8 010a 0000 0000 ....?..?........ 0x0020 0000 0000 0000 0000 0000 0000 0000 068b ................ 0x0030 77c8 w. 10:42:50.321473 192.168.1.10.2070 > 192.168.1.1.tftp: 45...