Hi all
Question 1:
I follow this instruction https://github.com/gluster/gluster-block, I use 2
gluster01 (192.168.101.110), gluster02 (192.168.101.111) and create one
gluster volume (block-storage). And use gluster-block to create block
storage (block-store/win)
[root@gluster01 ~]# gluster-block
Correct, you should stop clients, then servers, make 100% sure all
processes are dead:
Sometimes the brick process dont die, so killall glustefs and kilall glustefsd
will be needed.
Once all gluster services are shut down apply your updates. Then start
glusterd on the servers then run gluster v
These symptoms appear to be the same as I've recorded in this post:
http://lists.gluster.org/pipermail/gluster-users/2017-September/032435.html
On Wed, Sep 13, 2017 at 7:01 AM, Atin Mukherjee
wrote:
> Additionally the brick log file of the same brick would be
If you encounter issues where bricks and/or sometimes self-heal daemon fail
to start, please see these bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1491059
https://bugzilla.redhat.com/show_bug.cgi?id=1491060
The above bugs are filed against 3.10.4.
and this post where the OP was running
Nope, not gonna work... I could never go even from 3.6. to 3.7 without
downtime cause of the settings change, see:
http://lists.gluster.org/pipermail/gluster-users.old/2015-September/023470.html
Even when changing options in the older 3.6.x I had installed, my new
3.7.x server would not connect,
I ran into something like this in 3.10.4 and filed two bugs for it:
https://bugzilla.redhat.com/show_bug.cgi?id=1491059
https://bugzilla.redhat.com/show_bug.cgi?id=1491060
Please see the above bugs for full detail.
In summary, my issue was related to glusterd's pid handling of pid files
when is
I was looking to upgrade Gluster server from ver 3.5.X to 3.8.X.
I have already tried it in offline upgrade mode and that works, I am
interested in knowing if this upgrade of gluster server version can be
in online upgrade mode.
Many thanks in advance.
--
- Hemant Mamtora
Hi Amudhan,
Replies inline.
On Fri, Sep 8, 2017 at 6:37 AM, Amudhan P wrote:
> Hi,
>
> I am using glusterfs 3.10.1 with 30 nodes each with 36 bricks and 10 nodes
> each with 16 bricks in a single cluster.
>
> By default I have paused scrub process to have it run manually.
Hi Prasanna.
I follow this instruction https://github.com/gluster/gluster-block, I use 2
gluster01,02 and create one gluster volume. when I user Window Server 2012
(iSCSI Initiator) to connect to iSCSI target over, it's connected but in
Window don't recognize storage.
Size of gluster volume is
Thanks so much your answers.
I will try gluster-block.
2017-09-13 18:34 GMT+07:00 Prasanna Kalever :
> On Wed, Sep 13, 2017 at 1:03 PM, GiangCoi Mr wrote:
> > Hi all
> >
>
> Hi GiangCoi,
>
> The Good news is that now we have gluster-block [1] which
I emailed the logs earlier to just you.
On 13/09/17 11:58, Gaurav Yadav wrote:
Please send me the logs as well i.e glusterd.logs and
cmd_history.log.
On Wed, Sep 13, 2017 at 1:45 PM, lejeczek
> wrote:
On 13/09/17 06:21, Gaurav Yadav
On Wed, Sep 13, 2017 at 1:03 PM, GiangCoi Mr wrote:
> Hi all
>
Hi GiangCoi,
The Good news is that now we have gluster-block [1] which will help
you configure block storage using gluster very easy.
gluster-block will take care of all the targetcli and tcmu-runner
Hi guys.
A lot time with no words from me.
My GlustreFS setup is still alive and running for VM on 3.6.x version
Now I'm going to build a pretty large and scalable distributed storage and
some kind of smaller replicated.
Which version is recommended atm? I've read some notices on performance
Additionally the brick log file of the same brick would be required. Please
look for if brick process went down or crashed. Doing a volume start force
should resolve the issue.
On Wed, 13 Sep 2017 at 16:28, Gaurav Yadav wrote:
> Please send me the logs as well i.e
Please send me the logs as well i.e glusterd.logs and cmd_history.log.
On Wed, Sep 13, 2017 at 1:45 PM, lejeczek wrote:
>
>
> On 13/09/17 06:21, Gaurav Yadav wrote:
>
>> Please provide the output of gluster volume info, gluster volume status
>> and gluster peer status.
>>
On 13/09/17 06:21, Gaurav Yadav wrote:
Please provide the output of gluster volume info, gluster
volume status and gluster peer status.
ApartĀ from above info, please provide glusterd logs,
cmd_history.log.
Thanks
Gaurav
On Tue, Sep 12, 2017 at 2:22 PM, lejeczek
On 12/09/17 12:59, Niels de Vos wrote:
On Tue, Sep 12, 2017 at 10:01:14AM +0100, lejeczek wrote:
@devel
hi, I wonder who takes care of man pages when it comes to rpms?
I'd like to file a bugzilla report and would like to make sure it's packages
mainainer(s) are responsible for incomplete man
Hi all
I want to configure glusterfs to expose iSCSI target. I followed this
artical
https://pkalever.wordpress.com/2016/06/23/gluster-solution-for-non-shared-persistent-storage-in-docker-container/
but when I install tcmu-runner. It doesn't work.
I setup on CentOS7 and installed tcmu-runner by
18 matches
Mail list logo