similar to: Prevent total volume size reduction

Le 13/11/2017 ? 21:07, Daniel Berteaud a ?crit?: > > Le 13/11/2017 ? 10:04, Daniel Berteaud a ?crit?: >> >> Could I just remove the content of the brick (including the >> .glusterfs directory) and reconnect ? >> > > In fact, what would be the difference between reconnecting the brick > with a wiped FS, and using > > gluster volume remove-brick vmstore

Le 13/11/2017 ? 10:04, Daniel Berteaud a ?crit?: > > Could I just remove the content of the brick (including the .glusterfs > directory) and reconnect ? > In fact, what would be the difference between reconnecting the brick with a wiped FS, and using gluster volume remove-brick vmstore replica 1 master1:/mnt/bricks/vmstore gluster volume add-brick myvol replica 2

On 11/15/2017 12:54 PM, Daniel Berteaud wrote: > > > > Le 13/11/2017 ? 21:07, Daniel Berteaud a ?crit?: >> >> Le 13/11/2017 ? 10:04, Daniel Berteaud a ?crit?: >>> >>> Could I just remove the content of the brick (including the >>> .glusterfs directory) and reconnect ? >>> >> If it is only the brick that is faulty on the bad node,

Hi everyone. I'm running a simple Gluster setup like this: ? * Replicate 2x1 ? * Only 2 nodes, with one brick each ? * Nodes are CentOS 7.0, uising GlusterFS 3.5.3 (yes, I know it's old, I just can't upgrade right now) No sharding or anything "fancy". This Gluster volume is used to host VM images, and are used by both nodes (which are gluster server and clients).

Le Jeudi, Novembre 16, 2017 13:07 CET, Ravishankar N <ravishankar at redhat.com> a ?crit: > On 11/16/2017 12:54 PM, Daniel Berteaud wrote: > > Any way in this situation to check which file will be healed from > > which brick before reconnecting ? Using some getfattr tricks ? > Yes, there are afr xattrs that determine the heal direction for each > file. The good copy

On 11/16/2017 12:54 PM, Daniel Berteaud wrote: > Le 15/11/2017 ? 09:45, Ravishankar N a ?crit?: >> If it is only the brick that is faulty on the bad node, but >> everything else is fine, like glusterd running, the node being a part >> of the trusted storage pool etc,? you could just kill the brick first >> and do step-13 in "10.6.2. Replacing a Host Machine with

Le 15/11/2017 ? 09:45, Ravishankar N a ?crit?: > If it is only the brick that is faulty on the bad node, but everything > else is fine, like glusterd running, the node being a part of the > trusted storage pool etc,? you could just kill the brick first and do > step-13 in "10.6.2. Replacing a Host Machine with the Same Hostname", > (the mkdir of non-existent dir,

On 11/17/2017 03:41 PM, Daniel Berteaud wrote: > Le Jeudi, Novembre 16, 2017 13:07 CET, Ravishankar N <ravishankar at redhat.com> a ?crit: > >> On 11/16/2017 12:54 PM, Daniel Berteaud wrote: >>> Any way in this situation to check which file will be healed from >>> which brick before reconnecting ? Using some getfattr tricks ? >> Yes, there are afr

Le 15/11/2017 à 19:23, Andrew Bartlett via samba a écrit : >> You have 'add machine script = /usr/local/bin/addworkstation.pl "%u"' >> Try removing the double quotes. >> >> There isn't doesn't see to be anything else really wrong with your >> smb.conf. >> > G'Day Rowland, > > While it is possible our parsing of the smb.conf

Hi. I'm running samba 3.6.3 (on Ubuntu 12.04). This server is acting as an old style NT4 domain using samba as backend. Machine accounts are created using a script, called by samba (add machine script). Everything is working great. Now, I want to keep the same thing, but on Ubuntu 16.04, so with samba 4.3.11. Mostly everything is working as expected, except that smbd doesn't execute the

Thanks for your response Le Mercredi, Novembre 15, 2017 17:38 CET, Rowland Penny via samba <samba at lists.samba.org> a écrit: > I suppose the obvious question is, is the script executable ? It is. It's a simple perl script with +x. I can exec it from the comande line like /usr/local/bin/addworkstation.pl foo$ which creates the machin account like it should. I've also

Le Jeudi, Novembre 16, 2017 09:35 CET, Rowland Penny <rpenny at samba.org> a écrit: > > This may have nothing to do with Samba, if you are running sssd, then > this will be doing the authentication. sssd was providing the NSS -> LDAP layer, just like nss-ldap would do (it also provides a pam module equivalent to pam-ldap for UNIX accounts) > If you are running sssd, try

Hi, I'm running into problems with blockcommit and gluster network disks - wanted to check how to pass path for network disks. How's the protocol and host parameters specified? For a backing volume chain as below, executing virsh blockcommit fioo5 vmstore/912d9062-3881-479b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6d8a4/027a3b37-77d4-4fa9-8173-b1fedba1176c --base

On Thu, 2017-11-16 at 09:53 +0100, Daniel Berteaud via samba wrote: > Le Jeudi, Novembre 16, 2017 09:35 CET, Rowland Penny <rpenny at samba.org> a écrit: > > > > This may have nothing to do with Samba, if you are running sssd, then > > this will be doing the authentication. > > sssd was providing the NSS -> LDAP layer, just like nss-ldap would do > (it

I recently began getting periodic emails from SEalert that SELinux is preventing /usr/libexec/qemu-kvm "getattr" access from the directory I store all my virtual machines for KVM. All VMs are stored under /vmstore , which is it's own mount point, and every file and folder under /vmstore currently has the correct context that was set by doing the following: semanage fcontext -a -t

On Wed, 2017-11-15 at 17:58 +0000, Rowland Penny via samba wrote: > On Wed, 15 Nov 2017 18:01:51 +0100 > "Daniel Berteaud" <daniel at firewall-services.com> wrote: > > > Thanks for your response > > > > Le Mercredi, Novembre 15, 2017 17:38 CET, Rowland Penny via samba > > <samba at lists.samba.org> a écrit: > > > > > I

----- Forwarded by FWSDevelopment/FWS/DOI on 02/25/2003 03:45 PM ----- |---------+----------------------------------------------> | | "Florian Stahl" | | | <fstahl@xantury.com> | | | Sent by: | | | samba-bounces+ascannel=fws.gov@list| | |

Attempting to take snapshots of VM using virsh with the following command, # virsh -c qemu:///system snapshot-create CentOS6-x86-001 Results in the following error, error: internal error unable to execute QEMU command 'savevm': The command savevm has not been found The VM's virtual disks are qcow2. Below is the XML file for this vm ------------ <domain type='kvm'

On Thu, 16 Nov 2017 08:20:03 +0100 Daniel Berteaud via samba <samba at lists.samba.org> wrote: > Now, the "funny" thing is that, it did work, something like 3 times > in over 50 tries. It's not just the config because, once it worked, I > removed the same workstation from the domain, removed the LDAP entry, > made no configuration change, not service restart and

Attempting to take snapshots of VM using virsh with the following command, # virsh -c qemu:///system snapshot-create CentOS6-x86-001 Results in the following error, error: internal error unable to execute QEMU command 'savevm': The command savevm has not been found The VM's virtual disks are qcow2. Below is the XML file for this vm ------------ <domain type='kvm'