Vijay,
Is there any bugzilla item for this issue? So I could track if there is
some bugfix on it then I could backport to my deployment :)
On Wed, Apr 23, 2014 at 6:34 AM, Vijay Bellur wrote:
> On 04/22/2014 01:53 PM, Vijay Bellur wrote:
>
>> On 04/21/2014 11:42 PM, Mingfan Lu wrote:
>>
>>> y
On 04/22/2014 01:53 PM, Vijay Bellur wrote:
On 04/21/2014 11:42 PM, Mingfan Lu wrote:
yes. After I restart the volume, it works. But it should be a
workaround for sometimes it is impossible to restart the volume in
proeuction envriment.
Right, ideally it should not require a restart. Can you
On 04/21/2014 11:42 PM, Mingfan Lu wrote:
yes. After I restart the volume, it works. But it should be a
workaround for sometimes it is impossible to restart the volume in
proeuction envriment.
Right, ideally it should not require a restart. Can you please provide
output of gluster volume inf
yes. After I restart the volume, it works. But it should be a workaround
for sometimes it is impossible to restart the volume in proeuction
envriment.
On Tue, Apr 22, 2014 at 2:09 PM, Humble Devassy Chirammal <
humble.deva...@gmail.com> wrote:
> Hi Mingfan,
>
> Can you please try to restart the
Hi Mingfan,
Can you please try to restart the subjected volume [1] and find the result?
http://review.gluster.org/#/c/7412/7/doc/release-notes/3.5.0.md
--Humble
On Tue, Apr 22, 2014 at 10:46 AM, Mingfan Lu wrote:
> I saw something in
> https://forge.gluster.org/gluster-docs-project/pages/Gl
I saw something in
https://forge.gluster.org/gluster-docs-project/pages/GlusterFS_34_Release_Notes
I wonder whether I should restart the glusterd?
Known Issues:
-
The following configuration changes are necessary for qemu and samba
integration with libgfapi to work seamlessly:
1
I have created a volume named test_auth and set server.allow-insecure on
Volume Name: test_auth
Type: Distribute
Volume ID: d9bdc43e-15ce-4072-8d89-a34063e82427
Status: Started
Number of Bricks: 3
Transport-type: tcp
Bricks:
Brick1: server1:/mnt/xfsd/test_auth
Brick2: server2:/mnt/xfsd/test_auth
B
