Adding the list, in order to have other people's opinions...
Today, the Monday after day light saving time change, I have only half a neuron on duty, so, "reply to all" is a task next-to-impossible.
---------- Forwarded message ----------
From: Carlos Capriotti <capriotti.carlos@xxxxxxxxx>
Date: Mon, Mar 31, 2014 at 2:50 PM
Subject: Re: Capturing config in a file
To: Steve Thomas <sthomas@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
From: Carlos Capriotti <capriotti.carlos@xxxxxxxxx>
Date: Mon, Mar 31, 2014 at 2:50 PM
Subject: Re: Capturing config in a file
To: Steve Thomas <sthomas@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Steve:
Capturing config on a file CAN be done, BUt, using that config is another story.
What I did when I needed it:
gluster volume info <yourvolumenamehere> >> glusterconf.txt
next edit that file, trimming whatever unnecessary info it has, untill it looks like this:
nfs.trusted-sync on
nfs.addr-namelookup off
nfs.nlm off
network.ping-timeout 20
performance.quick-read off
performance.read-ahead off
performance.io-cache off
performance.stat-prefetch off
cluster.eager-lock enable
network.remote-dio on
performance.cache-max-file-size 2MB
performance.cache-refresh-timeout 4
performance.cache-size 1GB
performance.write-behind-window-size 4MB
performance.io-thread-count 32
And then use this very simple script, using your glusterconf.txt file as a parameter, to duplicate your settings on your volume:
#!/bin/bash
while read line; do
echo $line
gluster volume set vmdata $line
done < $1
Of course there is a lot of room for improvement, but that gets the job done.
Cheers,
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
