search for: 40bd

...h name and path of the file that caused the failure. Unable to update computer policy successfully. The following error s were found: Group Policy was not processed. Windows was unable to apply the settings registry-based policy for the LDAP Group Policy object LDAP://CN =Machine,cn={69A4F8E5-0693-40BD-9F0D-845DD5AA342C},cn=policies,cn=system,DC=inte rno,DC=XXXXX,DC=XXX,DC=br . The Group Policy settings will not be r resolved until this event is resolved. View event details for more information about the path name and path of the file that caused the failure. The following warnings were encounte...

...ghly 8 million reads and 100k writes daily.) The heal info output is full of lines like this: ... Brick gv2:/data/glusterfs <gfid:96a4ee35-b519-40e2-8dc0-a26f8faa5628> <gfid:fa4185b0-e5ab-4fdc-9dca-cb6ba33dcc8d> <gfid:8b2cf4bf-8c2a-465e-8f28-3e9a7f517268> <gfid:13925c48-fda4-40bd-bfcb-d7ced99b82b2> <gfid:292e3a0e-7114-4c97-b688-e94503047b58> <gfid:a52d1173-e034-4b57-9170-a7c91cbe2904> <gfid:5c830c7b-97b7-425b-9ab2-761ef2f41e88> <gfid:420c76a8-1598-4136-9c77-88c8d59d24e7> <gfid:ea6dbca2-f7e3-4015-ae34-04e8bf31fd4f> ... And so forth. Out of 8...

...hat caused the failure. > Unable to update computer policy successfully. The following error > s were found: > > Group Policy was not processed. Windows was unable to apply the settings > registry-based policy for the LDAP Group Policy object LDAP://CN > =Machine,cn={69A4F8E5-0693-40BD-9F0D-845DD5AA342C},cn=policies,cn=system,DC=inte > > rno,DC=XXXXX,DC=XXX,DC=br . The Group Policy settings will not be r > resolved until this event is resolved. View event details for > more information about the path name and path of the file that caused > the failure. > The f...

...info summary is supported from version 3.13. The heal info output is full of lines like this: ... Brick gv2:/data/glusterfs <gfid:96a4ee35-b519-40e2-8dc0-a26f8faa5628> <gfid:fa4185b0-e5ab-4fdc-9dca-cb6ba33dcc8d> <gfid:8b2cf4bf-8c2a-465e-8f28-3e9a7f517268> <gfid:13925c48-fda4-40bd-bfcb-d7ced99b82b2> <gfid:292e3a0e-7114-4c97-b688-e94503047b58> <gfid:a52d1173-e034-4b57-9170-a7c91cbe2904> <gfid:5c830c7b-97b7-425b-9ab2-761ef2f41e88> <gfid:420c76a8-1598-4136-9c77-88c8d59d24e7> <gfid:ea6dbca2-f7e3-4015-ae34-04e8bf31fd4f> ... And so forth. Out of 8...

Hi folks, I'm troubled moving an arbiter brick to another server because of I/O load issues. My setup is as follows: # gluster volume info Volume Name: myvol Type: Distributed-Replicate Volume ID: 43ba517a-ac09-461e-99da-a197759a7dc8 Status: Started Snapshot Count: 0 Number of Bricks: 3 x (2 + 1) = 9 Transport-type: tcp Bricks: Brick1: gv0:/data/glusterfs Brick2: gv1:/data/glusterfs Brick3:

Hello, copying idmap is fairly straightforward. 1) on your first DC (that one that has PDC FSMO, and is the source for rsync) create backup of idmap.ldb tdbbackup -s .bak /path/to/samba/private/idmap.ldb it will create idmap.ldb.bak 2) stop samba service on second DC 3) copy idmap.ldb.bak from first dc to second dc, lose the .bak suffix and just copy it over idmap.ldb on second dc 4)