search for: 46d9

...nel at boot time, should be able to archive that. However it is not the case in my exercise. These are what I have now $ grep CONFIG_MEMCG_KMEM /boot/config-3.10.0-327.36.3.el7.x86_64 CONFIG_MEMCG_KMEM=y $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.10.0-327.36.3.el7.x86_64 root=UUID=56568066-5719-46d9-981d-278c7559689b ro quiet cgroup.memory=nokmem systemd.log_level=debug But kernel memory is still accounted in user's applications. Any suggestion on how to chase the issue is greatly appreciated! Thank you! Best Regards, Wensheng

...~]# cat fix.ldif dn: CN=Domain Users,CN=Users,DC=EXAMPLE,DC=COM changetype: modify delete: member member: CN=mstudtma,OU=Industries Users,DC=EXAMPLE,DC=COM - === dbcheck === ERROR: incorrect GUID component for member in object CN=Domain Users,CN=Users,DC=EXAMPLE,DC=COM - <GUID=4adc8e8c-db48-46d9-9a55 -1f222350d4fa>;CN=mstudtma,OU=Industries Users,DC=EXAMPLE,DC=COM unable to find object for DN CN=mstudtma,OU=Industries Users,DC=EXAMPLE,DC=COM - (No such Base DN: CN=mstudtma,OU=Industries Users,DC=EXAMPLE,DC=COM) Not removing dangling forward link -- Adam Tauno Williams <mailto:awil...

...n accordance with the VDDK > - * documentation, we must do all open/close calls from a single > - * thread. This is a huge pain. > +/* The rules on threads and VDDK are here: > + * > https://code.vmware.com/docs/11750/virtual-disk-development-kit-programming-guide/GUID-6BE903E8-DC70-46D9-98E4-E34A2002C2AD.html > + * > + * Before nbdkit 1.22 we used SERIALIZE_ALL_REQUESTS. Since nbdkit > + * 1.22 we changed this to SERIALIZE_REQUESTS and added a mutex around > + * calls to VixDiskLib_Open and VixDiskLib_Close. This is not quite > + * within the letter of the rules,...

...b/89a36b1fab8302ddc370695d386a28a03a74eae7/plugins/vddk/vddk.c#L505 > > I may have a play around with this tomorrow. The threading model allowed by VDDK is restrictive. The rules are here: https://code.vmware.com/docs/11750/virtual-disk-development-kit-programming-guide/GUID-6BE903E8-DC70-46D9-98E4-E34A2002C2AD.html I did a bit of testing, and it's possible to do better than what we are doing at the moment. Not sure at present if this will be easy or will add a lot of complexity. Read on ... I found through experimentation that it is possible to open multiple VDDK handles pointin...

I believe this roughly implements Nir's proposal here: https://www.redhat.com/archives/libguestfs/2020-August/msg00028.html Unfortunately it doesn't work for me. It actually slows things down quite a lot, for reasons I don't understand. Note the adjustment of the pool-max parameter and how it affects the total time. The results are quite reproducible. $ ./nbdkit -r -U - vddk

...the case in my exercise. These are what I have now >> $ grep CONFIG_MEMCG_KMEM /boot/config-3.10.0-327.36.3.el7.x86_64 >> >> CONFIG_MEMCG_KMEM=y >> >> $ cat /proc/cmdline >> >> BOOT_IMAGE=/vmlinuz-3.10.0-327.36.3.el7.x86_64 >> root=UUID=56568066-5719-46d9-981d-278c7559689b ro quiet >> cgroup.memory=nokmem >> systemd.log_level=debug >> >> But kernel memory is still accounted in user's applications. Any >> suggestion >> on how to chase the issue is greatly appreciated! Thank you! >> >> >> Best...

...do threading correctly in accordance with the VDDK - * documentation, we must do all open/close calls from a single - * thread. This is a huge pain. +/* The rules on threads and VDDK are here: + * https://code.vmware.com/docs/11750/virtual-disk-development-kit-programming-guide/GUID-6BE903E8-DC70-46D9-98E4-E34A2002C2AD.html + * + * Before nbdkit 1.22 we used SERIALIZE_ALL_REQUESTS. Since nbdkit + * 1.22 we changed this to SERIALIZE_REQUESTS and added a mutex around + * calls to VixDiskLib_Open and VixDiskLib_Close. This is not quite + * within the letter of the rules, but is within the spirit....

...do threading correctly in accordance with the VDDK - * documentation, we must do all open/close calls from a single - * thread. This is a huge pain. +/* The rules on threads and VDDK are here: + * https://code.vmware.com/docs/11750/virtual-disk-development-kit-programming-guide/GUID-6BE903E8-DC70-46D9-98E4-E34A2002C2AD.html + * + * Before nbdkit 1.22 we used SERIALIZE_ALL_REQUESTS. Since nbdkit + * 1.22 we changed this to SERIALIZE_REQUESTS and added a mutex around + * calls to VixDiskLib_Open and VixDiskLib_Close. This is not quite + * within the letter of the rules, but is within the spirit....

...at. > > However it is not the case in my exercise. These are what I have now > $ grep CONFIG_MEMCG_KMEM /boot/config-3.10.0-327.36.3.el7.x86_64 > > CONFIG_MEMCG_KMEM=y > > $ cat /proc/cmdline > > BOOT_IMAGE=/vmlinuz-3.10.0-327.36.3.el7.x86_64 > root=UUID=56568066-5719-46d9-981d-278c7559689b ro quiet cgroup.memory=nokmem > systemd.log_level=debug > > But kernel memory is still accounted in user's applications. Any suggestion > on how to chase the issue is greatly appreciated! Thank you! > > > Best Regards, > Wensheng > _________________...

...=EXAMPLE,DC=COM > changetype: modify > delete: member > member: CN=mstudtma,OU=Industries Users,DC=EXAMPLE,DC=COM > - > > > === dbcheck === > > ERROR: incorrect GUID component for member in object CN=Domain > Users,CN=Users,DC=EXAMPLE,DC=COM - <GUID=4adc8e8c-db48-46d9-9a55 > -1f222350d4fa>;CN=mstudtma,OU=Industries Users,DC=EXAMPLE,DC=COM > unable to find object for DN CN=mstudtma,OU=Industries > Users,DC=EXAMPLE,DC=COM - (No such Base DN: CN=mstudtma,OU=Industries > Users,DC=EXAMPLE,DC=COM) > Not removing dangling forward link It is harmless,...

...453444444 Mar 18 23:41:01 DEBUG[10406]: Detecting DTMF inband with sw DSP on /dev/ttyI1 Mar 18 23:41:01 DEBUG[10406]: Dropping duplicate answer! Mar 18 23:41:01 VERBOSE[10406]: -- Modem[i4l]/ttyI1 answered SIP/201-3e46 Mar 18 23:41:01 DEBUG[10406]: Stopping retransmission on '57DF3381-B90C-46D9-9666-99FF5F1CBCCD@172.16.0.53' of Response 55994: Found Mar 18 23:41:01 DEBUG[10406]: Ooh, format changed from unknown to alaw Mar 18 23:41:06 DEBUG[10406]: Didn't get a frame from channel: SIP/201-3e46 Mar 18 23:41:06 DEBUG[10406]: Bridge stops bridging channels SIP/201-3e46 and Modem[i4l]...

In theory this patch depends on this series: https://www.redhat.com/archives/libguestfs/2020-August/msg00021.html In practice I believe they're independent of each other, but the above series makes it easier to test. Rich.

...86a28a03a74eae7/plugins/vddk/vddk.c#L505 > > > > I may have a play around with this tomorrow. > > The threading model allowed by VDDK is restrictive. The rules are here: > > https://code.vmware.com/docs/11750/virtual-disk-development-kit-programming-guide/GUID-6BE903E8-DC70-46D9-98E4-E34A2002C2AD.html > > I did a bit of testing, and it's possible to do better than what we > are doing at the moment. Not sure at present if this will be easy or > will add a lot of complexity. Read on ... > > I found through experimentation that it is possible to open m...

...else if (strcmp (key, "reexeced_") == 0) { /* Special name because it is only for internal use. */ reexeced = (char *)value; @@ -482,20 +490,37 @@ vddk_dump_plugin (void) * https://code.vmware.com/docs/11750/virtual-disk-development-kit-programming-guide/GUID-6BE903E8-DC70-46D9-98E4-E34A2002C2AD.html * * Before nbdkit 1.22 we used SERIALIZE_ALL_REQUESTS. Since nbdkit - * 1.22 we changed this to SERIALIZE_REQUESTS and added a mutex around - * calls to VixDiskLib_Open and VixDiskLib_Close. This is not quite - * within the letter of the rules, but is within the spirit....

Hi , I have installed "ruby 1.9.3p429 " already but as per my project required i want downgrade to "1.8.7-p371" while tying with the below command i am getting the below error message , please let me know how to solve this issue ? *COMMAND : **rbenv install 1.8.7-p371* * * Downloading ruby-1.8.7-p371.tar.gz... ->

Nir, BTW what are you using for performance testing? As far as I can tell it's not possible to make qemu-img convert use multi-conn when connecting to the source (which is going to be a problem if we want to use this stuff in virt-v2v). Instead I've hacked up a copy of this program from libnbd: https://github.com/libguestfs/libnbd/blob/master/examples/threaded-reads-and-writes.c so

..."reexeced_") == 0) { > /* Special name because it is only for internal use. */ > reexeced = (char *)value; > @@ -482,20 +490,37 @@ vddk_dump_plugin (void) > * > https://code.vmware.com/docs/11750/virtual-disk-development-kit-programming-guide/GUID-6BE903E8-DC70-46D9-98E4-E34A2002C2AD.html > * > * Before nbdkit 1.22 we used SERIALIZE_ALL_REQUESTS. Since nbdkit > - * 1.22 we changed this to SERIALIZE_REQUESTS and added a mutex around > - * calls to VixDiskLib_Open and VixDiskLib_Close. This is not quite > - * within the letter of the rules,...

...453444444 Mar 18 23:41:01 DEBUG[10406]: Detecting DTMF inband with sw DSP on /dev/ttyI1 Mar 18 23:41:01 DEBUG[10406]: Dropping duplicate answer! Mar 18 23:41:01 VERBOSE[10406]: -- Modem[i4l]/ttyI1 answered SIP/201-3e46 Mar 18 23:41:01 DEBUG[10406]: Stopping retransmission on '57DF3381-B90C-46D9-9666-99FF5F1CBCCD@172.16.0.53' of Response 55994: Found Mar 18 23:41:01 DEBUG[10406]: Ooh, format changed from unknown to alaw Mar 18 23:41:06 DEBUG[10406]: Didn't get a frame from channel: SIP/201-3e46 Mar 18 23:41:06 DEBUG[10406]: Bridge stops bridging channels SIP/201-3e46 and Modem[i4l]...

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