Displaying 14 results from an estimated 14 matches for "f309".
Did you mean:
309
2018 Jan 25
2
Run away memory with gluster mount
...t sure how to
troubleshoot. I don't *think* this is expected behavior. This is on an
updated CentOS 7 box. The setup is a simple two node replicated layout
where the two nodes act as both server and client. The volume in
question: Volume Name: GlusterWWW Type: Replicate Volume ID:
8e9b0e79-f309-4d9b-a5bb-45d065faaaa3 Status: Started Snapshot Count: 0
Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1:
vs1dlan.mydomain.com:/glusterfs_bricks/brick1/www Brick2:
vs2dlan.mydomain.com:/glusterfs_bricks/brick1/www Options Reconfigured:
nfs.disable: on cluster.favorite-child-polic...
2018 Jan 25
0
Run away memory with gluster mount
...not sure how to troubleshoot. I don't *think* this is expected behavior.
This is on an updated CentOS 7 box. The setup is a simple two node replicated layout where the two nodes act as both server and client.
The volume in question:
Volume Name: GlusterWWW
Type: Replicate
Volume ID: 8e9b0e79-f309-4d9b-a5bb-45d065faaaa3
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: vs1dlan.mydomain.com:/glusterfs_bricks/brick1/www
Brick2: vs2dlan.mydomain.com:/glusterfs_bricks/brick1/www
Options Reconfigured:
nfs.disable: on
cluster.favorite-child-policy: m...
2018 Jan 26
2
Run away memory with gluster mount
...think* this is expected behavior.
>
> This is on an updated CentOS 7 box. The setup is a simple two node
> replicated layout where the two nodes act as both server and client.
>
> The volume in question:
>
> Volume Name: GlusterWWW
> Type: Replicate
> Volume ID: 8e9b0e79-f309-4d9b-a5bb-45d065faaaa3
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 1 x 2 = 2
> Transport-type: tcp
> Bricks:
> Brick1: vs1dlan.mydomain.com:/glusterfs_bricks/brick1/www
> Brick2: vs2dlan.mydomain.com:/glusterfs_bricks/brick1/www
> Options Reconfigured:
> nfs...
2018 Jan 27
6
Run away memory with gluster mount
...tOS 7 box. The setup is a simple two node
>>> replicated layout where the two nodes act as both server and
>>> client.
>>>
>>> The volume in question:
>>>
>>> Volume Name: GlusterWWW
>>> Type: Replicate
>>> Volume ID: 8e9b0e79-f309-4d9b-a5bb-45d065faaaa3
>>> Status: Started
>>> Snapshot Count: 0
>>> Number of Bricks: 1 x 2 = 2
>>> Transport-type: tcp
>>> Bricks:
>>> Brick1: vs1dlan.mydomain.com:/glusterfs_bricks/brick1/www
>>> Brick2: vs2dlan.mydomain.com:/gluster...
2018 Jan 29
0
Run away memory with gluster mount
...e two node
>>>> replicated layout where the two nodes act as both server and
>>>> client.
>>>>
>>>> The volume in question:
>>>>
>>>> Volume Name: GlusterWWW
>>>> Type: Replicate
>>>> Volume ID: 8e9b0e79-f309-4d9b-a5bb-45d065faaaa3
>>>> Status: Started
>>>> Snapshot Count: 0
>>>> Number of Bricks: 1 x 2 = 2
>>>> Transport-type: tcp
>>>> Bricks:
>>>> Brick1: vs1dlan.mydomain.com:/glusterfs_bricks/brick1/www
>>>> Brick2: v...
2018 Jan 26
0
Run away memory with gluster mount
...gt;>
>> This is on an updated CentOS 7 box. The setup is a simple two node replicated layout where the two nodes act as both server and
>> client.
>>
>> The volume in question:
>>
>> Volume Name: GlusterWWW
>> Type: Replicate
>> Volume ID: 8e9b0e79-f309-4d9b-a5bb-45d065faaaa3
>> Status: Started
>> Snapshot Count: 0
>> Number of Bricks: 1 x 2 = 2
>> Transport-type: tcp
>> Bricks:
>> Brick1: vs1dlan.mydomain.com:/glusterfs_bricks/brick1/www
>> Brick2: vs2dlan.mydomain.com:/glusterfs_bricks/brick1/www
>>...
2018 Jan 29
0
Run away memory with gluster mount
...de
> >>> replicated layout where the two nodes act as both server and
> >>> client.
> >>>
> >>> The volume in question:
> >>>
> >>> Volume Name: GlusterWWW
> >>> Type: Replicate
> >>> Volume ID: 8e9b0e79-f309-4d9b-a5bb-45d065faaaa3
> >>> Status: Started
> >>> Snapshot Count: 0
> >>> Number of Bricks: 1 x 2 = 2
> >>> Transport-type: tcp
> >>> Bricks:
> >>> Brick1: vs1dlan.mydomain.com:/glusterfs_bricks/brick1/www
> >>> Br...
2018 Jan 29
2
Run away memory with gluster mount
...replicated layout where the two nodes act as both server and
>>>>> client.
>>>>>
>>>>> The volume in question:
>>>>>
>>>>> Volume Name: GlusterWWW
>>>>> Type: Replicate
>>>>> Volume ID: 8e9b0e79-f309-4d9b-a5bb-45d065faaaa3
>>>>> Status: Started
>>>>> Snapshot Count: 0
>>>>> Number of Bricks: 1 x 2 = 2
>>>>> Transport-type: tcp
>>>>> Bricks:
>>>>> Brick1: vs1dlan.mydomain.com:/glusterfs_bricks/brick1/www
&g...
2018 Jan 30
1
Run away memory with gluster mount
...es act as both server and
> >>>>> client.
> >>>>>
> >>>>> The volume in question:
> >>>>>
> >>>>> Volume Name: GlusterWWW
> >>>>> Type: Replicate
> >>>>> Volume ID: 8e9b0e79-f309-4d9b-a5bb-45d065faaaa3
> >>>>> Status: Started
> >>>>> Snapshot Count: 0
> >>>>> Number of Bricks: 1 x 2 = 2
> >>>>> Transport-type: tcp
> >>>>> Bricks:
> >>>>> Brick1: vs1dlan.mydomain.com:/...
2018 Feb 02
3
Run away memory with gluster mount
...;>> client.
>>>>>>>>
>>>>>>>> The volume in question:
>>>>>>>>
>>>>>>>> Volume Name: GlusterWWW
>>>>>>>> Type: Replicate
>>>>>>>> Volume ID: 8e9b0e79-f309-4d9b-a5bb-45d065faaaa3
>>>>>>>> Status: Started
>>>>>>>> Snapshot Count: 0
>>>>>>>> Number of Bricks: 1 x 2 = 2
>>>>>>>> Transport-type: tcp
>>>>>>>> Bricks:
>>>>>&...
2018 Feb 01
0
Run away memory with gluster mount
...and
>>>>>>> client.
>>>>>>>
>>>>>>> The volume in question:
>>>>>>>
>>>>>>> Volume Name: GlusterWWW
>>>>>>> Type: Replicate
>>>>>>> Volume ID: 8e9b0e79-f309-4d9b-a5bb-45d065faaaa3
>>>>>>> Status: Started
>>>>>>> Snapshot Count: 0
>>>>>>> Number of Bricks: 1 x 2 = 2
>>>>>>> Transport-type: tcp
>>>>>>> Bricks:
>>>>>>> Brick1: vs1d...
2018 Feb 03
0
Run away memory with gluster mount
...client.
>
> The volume in question:
>
> Volume Name: GlusterWWW
> Type: Replicate
> Volume ID:
> 8e9b0e79-f309-4d9b-a5bb-45d065faaaa3
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 1 x 2 = 2
> Transport-type: tcp
> Bricks:
&...
2018 Feb 21
1
Run away memory with gluster mount
...;
>> ??????????????????????????????? The volume in question:
>>
>> ??????????????????????????????? Volume Name: GlusterWWW
>> ??????????????????????????????? Type: Replicate
>> ??????????????????????????????? Volume ID:
>> ??????????????????????????????? 8e9b0e79-f309-4d9b-a5bb-45d065faaaa3
>> ??????????????????????????????? Status: Started
>> ??????????????????????????????? Snapshot Count: 0
>> ??????????????????????????????? Number of Bricks: 1 x 2 = 2
>> ??????????????????????????????? Transport-type: tcp
>> ?????????????????????...
2018 Feb 05
1
Run away memory with gluster mount
...> The volume in question:
> >
> > Volume Name: GlusterWWW
> > Type: Replicate
> > Volume ID:
> > 8e9b0e79-f309-4d9b-a5bb-45d065faaaa3
> > Status: Started
> > Snapshot Count: 0
> > Number of Bricks: 1 x 2 = 2
> > Transport-type: tcp
> >...