On 08/12/2014 10:59 PM, Jorick Astrego wrote:
On 08/12/2014 05:09 PM, Sahina Bose wrote:
On 08/12/2014 08:10 PM, Jorick Astrego wrote:
On 08/12/2014 03:44 PM, Sahina Bose wrote:
Could you provide the vdsm and supervdsm log from the node?
vdsm:
http://pastebin.com/edZrvnkr
(cut some
I think its worth to check the result of, some other verb to isolate this
issue . Can u try below in your host ?
#vdsClient -s localhost glusterHostsList
On Wed, Aug 13, 2014 at 11:45 AM, Sahina Bose sab...@redhat.com wrote:
On 08/12/2014 10:59 PM, Jorick Astrego wrote:
On 08/12/2014
On 08/13/2014 09:47 AM, Humble Devassy Chirammal wrote:
I think its worth to check the result of, some other verb to isolate
this issue . Can u try below in your host ?
#vdsClient -s localhost glusterHostsList
On Wed, Aug 13, 2014 at 11:45 AM, Sahina Bose sab...@redhat.com
Hi Jorick,
which version of GlusterFS are you using?
Try to restart glusterd on each of the bricks, then try to follow this link:
http://joejulian.name/blog/glusterfs-path-or-a-prefix-of-it-is-already-part-of-a-volume/
Please tell me if this helps
Regards,
Maor
- Original Message -
Hi,
No restarting glusterfsd doesn't help. The steps in the link you gave me
don't help either. The node is clean installed and has never been a part
of a glusterfs Running gluster version 3.5.2
glusterfs-server-3.5.2-1.el7.x86_64
glusterfs-api-3.5.2-1.el7.x86_64
Could you provide the vdsm and supervdsm log from the node?
On 08/12/2014 07:08 PM, Jorick Astrego wrote:
Hi,
No restarting glusterfsd doesn't help. The steps in the link you gave
me don't help either. The node is clean installed and has never been a
part of a glusterfs Running gluster
On 08/12/2014 03:44 PM, Sahina Bose wrote:
Could you provide the vdsm and supervdsm log from the node?
vdsm:
http://pastebin.com/edZrvnkr
(cut some repetitive loglines out to fit on pastebin)
Supervdsm:
http://pastebin.com/V8xTTMKk
On 08/12/2014 07:08 PM, Jorick Astrego wrote:
Hi,
No
On 08/12/2014 08:10 PM, Jorick Astrego wrote:
On 08/12/2014 03:44 PM, Sahina Bose wrote:
Could you provide the vdsm and supervdsm log from the node?
vdsm:
http://pastebin.com/edZrvnkr
(cut some repetitive loglines out to fit on pastebin)
Supervdsm:
http://pastebin.com/V8xTTMKk
I don't
On 08/12/2014 05:09 PM, Sahina Bose wrote:
On 08/12/2014 08:10 PM, Jorick Astrego wrote:
On 08/12/2014 03:44 PM, Sahina Bose wrote:
Could you provide the vdsm and supervdsm log from the node?
vdsm:
http://pastebin.com/edZrvnkr
(cut some repetitive loglines out to fit on pastebin)
Sorry forgot to add:
vdsClient -s localhost glusterVolumesList
Traceback (most recent call last):
File /usr/share/vdsm/vdsClient.py, line 2668, in module
code, message = commands[command][0](commandArgs)
File /usr/share/vdsm/vdsClientGluster.py, line 51, in
On 08/12/2014 08:31 PM, Jorick Astrego wrote:
Sorry forgot to add:
vdsClient -s localhost glusterVolumesList
Traceback (most recent call last):
File /usr/share/vdsm/vdsClient.py, line 2668, in module
code, message = commands[command][0](commandArgs)
File
On 08/12/2014 10:03 PM, Itamar Heim wrote:
On 08/12/2014 08:31 PM, Jorick Astrego wrote:
Sorry forgot to add:
vdsClient -s localhost glusterVolumesList
Traceback (most recent call last):
File /usr/share/vdsm/vdsClient.py, line 2668, in module
code, message =
12 matches
Mail list logo
