similar to: GlusterFS - Volume Backup and Restore and Monitor

Hi, I am working in Wipro Technologies India as a Technical Consultant. I am new to XEN Hypervisor [from http://wiki.xen.org/xenwiki/LiveCD]. Have downloaded "livecd-xen-3.2-0.8.2-i386.iso" and burned the XEN Live CD v2.0 . My development box is built with Windows XP SP3.Our Project is to use multiple Windows guest operating systems in XEN. Kindly guide me how to implement this

On Thu, Dec 22, 2016 at 10:36:01AM +0200, Ander Conselvan De Oliveira wrote: > On Wed, 2016-12-21 at 12:12 -0800, Dhinakaran Pandiyan wrote: > > This check is useful for drivers that do not have DRIVER_ATOMIC set but > > have atomic modesetting internally implemented. Wrap the check into a > > function since this is used in many places and as a bonus, the function > >

On Wed, 2016-12-21 at 12:12 -0800, Dhinakaran Pandiyan wrote: > This check is useful for drivers that do not have DRIVER_ATOMIC set but > have atomic modesetting internally implemented. Wrap the check into a > function since this is used in many places and as a bonus, the function > name helps to document what the check is for. > > v2: > Change return type to bool (Ville)

i915 does not set DRIVER_ATOMIC by default yet but uses atomic_check and atomic_commit. drm_object_property_get_value() does not read the correct value of atomic properties if DRIVER_ATOMIC is not set. Checking whether the driver uses atomic modeset is a better check instead as the property values are tracked in the state structures. v2: Included header Cc: Daniel Vetter <daniel.vetter at

i915 does not set DRIVER_ATOMIC by default yet but uses atomic_check and atomic_commit. drm_object_property_get_value() does not read the correct value of atomic properties if DRIVER_ATOMIC is not set. Checking whether the driver uses atomic modeset is a better check instead as the property values are tracked in the state structures. v2: Included header Cc: Daniel Vetter <daniel.vetter at

This check is useful for drivers that do not have DRIVER_ATOMIC set but have atomic modesetting internally implemented. Wrap the check into a function since this is used in many places and as a bonus, the function name helps to document what the check is for. v2: Change return type to bool (Ville) Move the function drm_atomic.h (Daniel) Fixed comment marker for documentation Suggested-by: Daniel

From: Dhinakaran Pandiyan <dhinakaran.pandiyan at intel.com> Currently we restrict the number of encoders that can be linked to a connector to 3, increase it to match the maximum number of encoders that can be initialized(32). To more effiently do that lets switch from an array of encoder ids to bitmask. v2: Fixing missed return on amdgpu_dm_connector_to_encoder() Suggested-by: Ville

This check is useful for drivers that do not have DRIVER_ATOMIC set but have atomic modesetting internally implemented. Wrap the check into a function since this is used in many places and as a bonus, the function name helps to document what the check is for. v2: Change return type to bool (Ville) Move the function drm_atomic.h (Daniel) Fixed comment marker for documentation v3: Included drmP.h

This check is useful for drivers that do not have DRIVER_ATOMIC set but have atomic modesetting internally implemented. Wrap the check into a function since this is used in many places and as a bonus, the function name helps to document what the check is for. v2: Change return type to bool (Ville) Move the function drm_atomic.h (Daniel) Suggested-by: Daniel Vetter <daniel.vetter at

From: Dhinakaran Pandiyan <dhinakaran.pandiyan at intel.com> Currently we restrict the number of encoders that can be linked to a connector to 3, increase it to match the maximum number of encoders that can be initialized(32). To more effiently do that lets switch from an array of encoder ids to bitmask. Also removing the best_encoder hook from the drivers that only have one encoder per

On Thu, Sep 05, 2019 at 02:09:27PM -0700, José Roberto de Souza wrote: > From: Dhinakaran Pandiyan <dhinakaran.pandiyan at intel.com> > > Currently we restrict the number of encoders that can be linked to > a connector to 3, increase it to match the maximum number of encoders > that can be initialized(32). > > To more effiently do that lets switch from an array of

A new intel-gpu-tools quarterly release is available with the following changes: General changes: - Bumped used C standard to gnu11. (Lucas De Marchi) - Bumped required meson version to 0.44. (Petri Latvala) - Introduced meson options for explicit control over optional dependencies. (Petri Latvala) - Added a meson option to set runpath for the installed executables. (Petri Latvala) -

From: Ville Syrjälä <ville.syrjala at linux.intel.com> Changes from the previous version mainly involve Danoie's suggestion of hiding the drm_encoder_find() in the iterator macro. I also polished the msm and tilcdc cases a bit more with another small helper. Cc: Alex Deucher <alexander.deucher at amd.com> Cc: amd-gfx at lists.freedesktop.org Cc: Ben Skeggs <bskeggs at

Hi everyone, I'm trying to recover a deleted LVM volume but can't see to get the syntax right. Running the following command gives me a list of backed up LVM volumes: root at usaxen02:[~]$ vgcfgrestore -l fluidVG_125094317679 ------- snip --------- File: /etc/lvm/archive/fluidVG_125094317679_00126-1479850541.vg VG name: fluidVG_125094317679 Description: Created

I wanted to call out Marco Agostini, who so kindly wrote up a post on using various tools to monitor GlusterFS performance: http://community.gluster.org/p/some-tools-to-monitor-performance/ Please review and comment as you see fit. If you find it helpful, let Marco know by clicking the "like" button. While we're on the subject of Monitoring GlusterFS, Gluster Superstar Craig

Dear gluster experts, I want to ask a question about how to monitor active mounted client for glusterfs. Since I want to known how many clients mount a volume and I also want to known the clients hostname/ip. I walk through the glusterfs admin guide and don't know how. Any one helps? -- Yongtao Fu -------------- next part -------------- An HTML attachment was scrubbed... URL:

Author: maybee Repository: /hg/zfs-crypto/gate Revision: fc2b4ea43f2c90b103d940d192c1e7f2306f9939 Log message: 6355162 ''zfs restore -d'' should not succeed upon a volume 6368561 zfs panic at zfs:zfsctl_snapdir_inactive() 6374110 ZFS Panic in zfs_lookup() during snapshot creation Files: update: usr/src/lib/libzfs/common/libzfs_dataset.c update:

Dear gluster experts, Recently I have restored one brick of my volume from hardware failure and everything works fine except that the volume status command report the resotred brick port as NA while the brick online statis is Y. What's wrong? Thank you. -- ???

Hi all? I do the following test? I create a glusterfs replica volume (replica count is 2 ) with two server node(server A and server B)? then mount the volume in client node? then? I shut down the network of server A node? in client node? I copy a dir?which has a lot of small files?? the dir size is 2.9GByte? when copy finish? I start the network of server A node? now?

Hey, How does distributed volume works with samba? I've got 2 servers with glusterfs. Each server is about 130 TB and acts like a brick for distributed volume. I've got samba up and running with vfs module on first server. Last night I've added the second server as a brick and rebalanced the volume with fix-layout option. I run glusterfs 3.8.9 on both machines. Samba share is running