search for: 4e9c

...1:43:47 +0000]: [99CE] S: A0004 OK Myrights completed. [08-Apr-2015 11:43:47 +0000]: [99CE] C: A0005 CREATE tam at crm.yb.lmax/Drafts/Test [08-Apr-2015 11:43:47 +0000]: [99CE] S: A0005 OK Create completed. Creating the subfolder as the local user itself works fine: [08-Apr-2015 11:35:35 +0000]: [4E9C] C: A0005 CREATE INBOX/Templates [08-Apr-2015 11:35:35 +0000]: [4E9C] S: A0005 OK Create completed. However the local user creates INBOX/Templates, whereas the ldap user is creating under tam at crm.yb.lmax/Templates. Is this an artifact of how we've set up namespaces below? Thanks, -Luke...

...devices,memory,cpuacct,cpu,ns,cpuset 0 0 .. $ chkconfig --list | grep cg cgconfig 0:off 1:off 2:off 3:off 4:off 5:off 6:off cgred 0:off 1:off 2:off 3:off 4:off 5:off 6:off xml definition -- <domain type="lxc"> <uuid>252a2dc5-452c-4e9c-a593-8c386c9f47e6</uuid> <name>instance-00000032</name> <memory>524288</memory> <vcpu>2</vcpu> <os> <type>exe</type> <cmdline>console=ttyS0</cmdline> <init>/sbin/init</init> </os> <c...

...wz--n- 5.36t 0 # pvs PV VG Fmt Attr PSize PFree /dev/sda3 vg0-sda lvm2 a-- 96.09g 15.96g /dev/sdb1 vg1-sdb lvm2 a-- 5.36t 0 tune2fs 1.41.12 (17-May-2010) Filesystem volume name: <none> Last mounted on: /vz Filesystem UUID: 74a4ea8b-03ed-4e9c-ab01-8574517cd5af Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount...

On 2017-04-20 18:38, Rowland Penny wrote: > On Thu, 20 Apr 2017 18:00:24 +0200 > Sven Schwedas via samba <samba at lists.samba.org> wrote: > >> On 2017-04-07 13:44, Sven Schwedas via samba wrote: >>> In the end I just upgraded all DCs to 4.5 and remote-deleted the >>> broken ones. Seemed to work without a hitch, manual removal was >>> only necessary

Situation: Trying to upgrade Samba from 4.1 to 4.5 without disruption too much by adding new DCs and demoting old ones. After bringing online the first 4.5 DC, I ran `demote --remove-other-dead-server=` on that DC to remove one of the old 4.1 DCs (held no FSMO roles). That seemed to run fine (the DC had been offline for a few weeks at that point and I didn't want to restore it just for

Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health

On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next

...306328AEDE4A9B4 (ec50dcb0-2dc7-4474-9ccf-2eeb7f739e48) on home-client-2 [2017-10-25 10:14:22.853891] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/E0AF6A8F6C53CD82E47A27ACBBB06F2E117D21FF (27f90a22-d06c-4e9c-b96b-86a41e9029da) on home-client-2 [2017-10-25 10:14:22.872582] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/791D360F96A16001B1EDA07DA80727182A5D96B9 (2252e0fe-590d-43d8-b3cb-06798d61d562) on home-cli...