search for: 6fa

...ation in the DMZ needs to access the directory via LDAP. When I tried to connect to the RODC using LDAP with simple bind, I always received the following error ldap_bind: Invalid credentials (49)         additional info: 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 6fa, v1db1 even though the credentials used are correct and do work with the "normal" DCs. I have already added the corresponding user to the group "Allowed RODC Password Replication Group", but that did not change anything... Authentication through Kerberos seems to work, but is...

...ss NIC: Intel 3945 ABG # uname -a SunOS appdev 5.11 snv_80 i86pc i386 i86xpv # isainfo -x amd64: ssse3 cx16 sse3 sse2 sse fxsr mmx cmov cx8 tsc fpu i386: ssse3 ahf cx16 sse3 sse2 sse fxsr mmx cmov cx8 tsc fpu # psrinfo -vp The physical processor has 2 virtual processors (0 1) x86 (GenuineIntel 6FA family 6 model 15 step 10 clock 2400 MHz) Intel(r) Core(tm)2 Duo CPU T7700 @ 2.40GHz Thoughts? This message posted from opensolaris.org

.../indices/xattrop > total 76180 > 10 drw------- 2 root root 4 Jul 29 12:15 . > 9 drw------- 5 root root 5 Apr 28 22:15 .. > 2798404 ---------- 2 root root 0 Apr 28 22:51 > 29e0d13e-1217-41cc-9bda-1fbbf781c397 > 2798404 ---------- 2 root root 0 Apr 28 22:51 > xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 > > > > I tried to find the real file on my brick where this xattrop file > points to using its inode number (command: find > /data/myvolume/brick/data -inum 8394642) but it does not find any > associated file. > > So my question here i...

...rfs/indices/xattrop >> total 76180 >> 10 drw------- 2 root root 4 Jul 29 12:15 . >> 9 drw------- 5 root root 5 Apr 28 22:15 .. >> 2798404 ---------- 2 root root 0 Apr 28 22:51 29e0d13e-1217-41cc-9bda-1fbbf781c397 >> 2798404 ---------- 2 root root 0 Apr 28 22:51 xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 >> I tried to find the real file on my brick where this xattrop file points to using its inode number (command: find /data/myvolume/brick/data -inum 8394642) but it does not find any associated file. >> So my question here is, is it possible that this is...

...e below: ls -lai /data/myvolume/brick/.glusterfs/indices/xattrop total 76180 10 drw------- 2 root root 4 Jul 29 12:15 . 9 drw------- 5 root root 5 Apr 28 22:15 .. 2798404 ---------- 2 root root 0 Apr 28 22:51 29e0d13e-1217-41cc-9bda-1fbbf781c397 2798404 ---------- 2 root root 0 Apr 28 22:51 xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 I tried to find the real file on my brick where this xattrop file points to using its inode number (command: find /data/myvolume/brick/data -inum 8394642) but it does not find any associated file. So my question here is, is it possible that this is a stale file whic...

...10 drw------- 2 root root 4 Jul 29 12:15 . >>> 9 drw------- 5 root root 5 Apr 28 22:15 .. >>> 2798404 ---------- 2 root root 0 Apr 28 22:51 >>> 29e0d13e-1217-41cc-9bda-1fbbf781c397 >>> 2798404 ---------- 2 root root 0 Apr 28 22:51 >>> xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 >>> >>> >>> >>> I tried to find the real file on my brick where this xattrop file >>> points to using its inode number (command: find >>> /data/myvolume/brick/data -inum 8394642) but it does not find any >&...

...e directory via LDAP. > > When I tried to connect to the RODC using LDAP with simple bind, I > always received the following error > > ldap_bind: Invalid credentials (49) > additional info: 80090308: LdapErr: DSID-0C0903A9, comment: > AcceptSecurityContext error, data 6fa, v1db1 > > even though the credentials used are correct and do work with the > "normal" DCs. > > I have already added the corresponding user to the group "Allowed RODC > Password Replication Group", but that did not change anything... > > Authenticatio...

...e directory via LDAP. > > When I tried to connect to the RODC using LDAP with simple bind, I > always received the following error > > ldap_bind: Invalid credentials (49) >         additional info: 80090308: LdapErr: DSID-0C0903A9, comment: > AcceptSecurityContext error, data 6fa, v1db1 > > even though the credentials used are correct and do work with the > "normal" DCs. > > I have already added the corresponding user to the group "Allowed RODC > Password Replication Group", but that did not change anything... > > Authenticatio...

...al 76180 >>>> 10 drw------- 2 root root 4 Jul 29 12:15 . >>>> 9 drw------- 5 root root 5 Apr 28 22:15 .. >>>> 2798404 ---------- 2 root root 0 Apr 28 22:51 29e0d13e-1217-41cc-9bda-1fbbf781c397 >>>> 2798404 ---------- 2 root root 0 Apr 28 22:51 xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 >>>> I tried to find the real file on my brick where this xattrop file points to using its inode number (command: find /data/myvolume/brick/data -inum 8394642) but it does not find any associated file. >>>> So my question here is, is it possi...

...2:15 . >>>>> 9 drw------- 5 root root 5 Apr 28 22:15 .. >>>>> 2798404 ---------- 2 root root 0 Apr 28 22:51 >>>>> 29e0d13e-1217-41cc-9bda-1fbbf781c397 >>>>> 2798404 ---------- 2 root root 0 Apr 28 22:51 >>>>> xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 >>>>> >>>>> >>>>> >>>>> I tried to find the real file on my brick where this xattrop file >>>>> points to using its inode number (command: find >>>>> /data/myvolume/brick/dat...

...me/brick/<REMOVED_DIRECTORIES_IN_BETWEEN>/fileKey node2: 2798404 1 ---------- 2 root root 0 Apr 28 22:51 /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 2798404 1 ---------- 2 root root 0 Apr 28 22:51 /data/myvolume/brick/.glusterfs/indices/xattrop/xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 arbirternode: NOTHING As you requested I have tried to run on node1 a getfattr on the fileKey file by using the following command: getfattr -m . -d -e hex fileKey but there is no output. I am not familiar with the getfattr command so maybe I am using the wrong param...

...> 2798404 1 ---------- 2 root root 0 Apr 28 22:51 > /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 > 2798404 1 ---------- 2 root root 0 Apr 28 22:51 > /data/myvolume/brick/.glusterfs/indices/xattrop/xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 > > arbirternode: > > NOTHING > > As you requested I have tried to run on node1 a getfattr on the > fileKey file by using the following command: > > getfattr -m . -d -e hex fileKey > > but there is no output. I am not familiar with...

...ORIES_IN_BETWEEN>/fileKey >> node2: >> 2798404 1 ---------- 2 root root 0 Apr 28 22:51 /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 >> 2798404 1 ---------- 2 root root 0 Apr 28 22:51 /data/myvolume/brick/.glusterfs/indices/xattrop/xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 >> arbirternode: >> NOTHING >> As you requested I have tried to run on node1 a getfattr on the fileKey file by using the following command: >> getfattr -m . -d -e hex fileKey >> but there is no output. I am not familiar with the getfatt...

...> >> When I tried to connect to the RODC using LDAP with simple bind, I >> always received the following error >> >> ldap_bind: Invalid credentials (49) >> additional info: 80090308: LdapErr: DSID-0C0903A9, comment: >> AcceptSecurityContext error, data 6fa, v1db1 >> >> even though the credentials used are correct and do work with the >> "normal" DCs. >> >> I have already added the corresponding user to the group "Allowed RODC >> Password Replication Group", but that did not change anything... &g...

...----- 2 root root 0 Apr 28 22:51 >>> /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 >>> 2798404 1 ---------- 2 root root 0 Apr 28 22:51 >>> /data/myvolume/brick/.glusterfs/indices/xattrop/xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 >>> >>> arbirternode: >>> >>> NOTHING >>> >>> As you requested I have tried to run on node1 a getfattr on the >>> fileKey file by using the following command: >>> >>> getfattr -m . -d...

https://bugs.freedesktop.org/show_bug.cgi?id=62914 Priority: medium Bug ID: 62914 Assignee: nouveau at lists.freedesktop.org Summary: ZaphodHeads doesn't work after upgrading to xorg 1.14 QA Contact: xorg-team at lists.x.org Severity: critical Classification: Unclassified OS: Linux (All) Reporter: