On Tue, Jun 26, 2012 at 02:08:42PM -0700, Simon Blackstein wrote:
Thanks Brian.
Yes, got rid of the .glusterfs and .vSphereHA directory that VMware
makes. Rebooted, so yes it was remounted and used a different mount
point name. Also got rid of attribute I found set on the root:
On Wed, Jun 27, 2012 at 12:23 AM, Brian Candler b.cand...@pobox.com wrote:
On Tue, Jun 26, 2012 at 02:08:42PM -0700, Simon Blackstein wrote:
Thanks Brian.
Yes, got rid of the .glusterfs and .vSphereHA directory that VMware
makes. Rebooted, so yes it was remounted and used a
To: Simon
Cc: gluster-users@gluster.org
Subject: Re: [Gluster-users] Gluster 3.3.0 and VMware ESXi 5
Simon - can you please try this patch: http://review.gluster.com/3617
Thanks,
Avati
On Mon, Jun 25, 2012 at 7:13 PM, Simon
si...@blackstein.commailto:si...@blackstein.com wrote:
I'm having
*Cc:* gluster-users@gluster.org
*Subject:* Re: [Gluster-users] Gluster 3.3.0 and VMware ESXi 5
** **
Simon - can you please try this patch: http://review.gluster.com/3617
** **
Thanks,
Avati
On Mon, Jun 25, 2012 at 7:13 PM, Simon si...@blackstein.com wrote:
I'm
:00
*To:* Simon
*Cc:* gluster-users@gluster.org
*Subject:* Re: [Gluster-users] Gluster 3.3.0 and VMware ESXi 5
** **
Simon - can you please try this patch: http://review.gluster.com/3617
** **
Thanks,
Avati
On Mon, Jun 25, 2012 at 7:13 PM, Simon si...@blackstein.com
Of *Anand Avati
*Sent:* 26 June 2012 04:00
*To:* Simon
*Cc:* gluster-users@gluster.org
*Subject:* Re: [Gluster-users] Gluster 3.3.0 and VMware ESXi 5
** **
Simon - can you please try this patch: http://review.gluster.com/3617***
*
** **
Thanks,
Avati
On Mon, Jun 25, 2012 at 7
Avati
*Sent:* 26 June 2012 04:00
*To:* Simon
*Cc:* gluster-users@gluster.org
*Subject:* Re: [Gluster-users] Gluster 3.3.0 and VMware ESXi 5
** **
Simon - can you please try this patch: http://review.gluster.com/3617**
**
** **
Thanks,
Avati
On Mon, Jun 25, 2012 at 7:13
it seems to run into the same trouble.
Fernando
From: Simon Blackstein [mailto:si...@blackstein.com]
Sent: 26 June 2012 18:01
To: Anand Avati
Cc: Fernando Frediani (Qube); gluster-users@gluster.org
Subject: Re: [Gluster-users] Gluster 3.3.0 and VMware ESXi 5
Honestly, I've been trying to reset
** **
*From:* Simon Blackstein [mailto:si...@blackstein.com]
*Sent:* 26 June 2012 18:01
*To:* Anand Avati
*Cc:* Fernando Frediani (Qube); gluster-users@gluster.org
*Subject:* Re: [Gluster-users] Gluster 3.3.0 and VMware ESXi 5
** **
Honestly, I've been trying to reset this volume
On Tue, Jun 26, 2012 at 10:01:21AM -0700, Simon Blackstein wrote:
Honestly, I've been trying to reset this volume completely to see if
the error was transitional but now getting the '/gfs or a prefix of it
is already part of a volume' message even after removing the attributes
from
Basically did all of that as previously noted:
setfattr -x trusted.gfid /gfs
setfattr -x trusted.glusterfs.volume-id /gfs
setfattr -x trusted.afr.gfs-vdi-client-0 /gfs
setfattr -x trusted.afr.gfs-vdi-client-1 /gfs
setfattr -x trusted.glusterfs.dht /gfs
On Tue, Jun 26, 2012 at 11:38 AM, Brian
On Tue, Jun 26, 2012 at 11:46:52AM -0700, Simon Blackstein wrote:
Basically did all of that as previously noted:
And rm -rf .glusterfs ?
If /gfs is the mountpoint, you could also try
unmount /gfs
rmdir /gfs
mkdir /gfs
and remount.
___
Thanks Brian.
Yes, got rid of the .glusterfs and .vSphereHA directory that VMware
makes. Rebooted, so yes it was remounted and used a different mount
point name. Also got rid of attribute I found set on the root:
setfattr -x trusted.gfid / setfattr -x trusted.glusterfs.dht /
Any other tips? :)
Can you get the output of getfattr -d -e hex -m . /gfs
Avati
On Jun 26, 2012 5:08 PM, Simon Blackstein si...@blackstein.com wrote:
Thanks Brian.
Yes, got rid of the .glusterfs and .vSphereHA directory that VMware
makes. Rebooted, so yes it was remounted and used a different mount
point
OK, figured this one out (my word this took some time). Found an
attribute set on the fourth node after running through them again.
Back to work... after patching all nodes and removing/recreating the
volume, this now works for me. Definitely not simple and please, if we can
clean up volumes
I'm having the same error deploying a green field ESXi 5.0 farm against
GlusterFS 3.3. Can provision a VM but can't start it with the identical error:
An unexpected error was received from the ESX host while powering on VM
vm-26941.
Failed to power on VM.
Unable to retrieve the current working
Simon - can you please try this patch: http://review.gluster.com/3617
Thanks,
Avati
On Mon, Jun 25, 2012 at 7:13 PM, Simon si...@blackstein.com wrote:
I'm having the same error deploying a green field ESXi 5.0 farm against
GlusterFS 3.3. Can provision a VM but can't start it with the
-users] Gluster 3.3.0 and VMware ESXi 5
Hi,
This logs way too much data too quickly, so I have cut the part of the nfs.log
for during the time I tried to power on the VM. Find it attached.
Regards,
Fernando
-Original Message-
From: gluster-users-boun...@gluster.org
[mailto:gluster
Bellur [mailto:vbel...@redhat.com]
Sent: 11 June 2012 17:54
To: Fernando Frediani (Qube)
Cc: 'Atha Kouroussis'; 'gluster-users@gluster.org'; Rajesh Amaravathi; Krishna
Srinivas
Subject: Re: [Gluster-users] Gluster 3.3.0 and VMware ESXi 5
On 06/11/2012 05:52 PM, Fernando Frediani (Qube) wrote
Kouroussis
Sent: 07 June 2012 15:29
To: gluster-users@gluster.org
Subject: [Gluster-users] Gluster 3.3.0 and VMware ESXi 5
Hi everybody,
we are testing Gluster 3.3 as an alternative to our current Nexenta based
storage. With the introduction of granular based locking gluster seems like a
viable
On 06/11/2012 05:52 PM, Fernando Frediani (Qube) wrote:
Was doing some read on RedHat website and found this URL which I wonder if the
problem would have anything to do with this:
http://docs.redhat.com/docs/en-US/Red_Hat_Storage_Software_Appliance/3.2/html/User_Guide/ch14s04s08.html
Although
-users@gluster.org
Subject: Re: [Gluster-users] Gluster 3.3.0 and VMware ESXi 5
Hi Fernando,
thanks for the reply. I'm seeing exactly the same behavior. I'm wondering if it
somehow has to do with locking. I read here
(http://community.gluster.org/q/can-not-mount-nfs-share-without-nolock-option
Hi everybody,
we are testing Gluster 3.3 as an alternative to our current Nexenta based
storage. With the introduction of granular based locking gluster seems like a
viable alternative for VM storage.
Regrettably we cannot get it to work even for the most rudimentary tests. We
have a two brick
15:29
To: gluster-users@gluster.org
Subject: [Gluster-users] Gluster 3.3.0 and VMware ESXi 5
Hi everybody,
we are testing Gluster 3.3 as an alternative to our current Nexenta based
storage. With the introduction of granular based locking gluster seems like a
viable alternative for VM storage
Kouroussis
Sent: 07 June 2012 15:29
To: gluster-users@gluster.org (mailto:gluster-users@gluster.org)
Subject: [Gluster-users] Gluster 3.3.0 and VMware ESXi 5
Hi everybody,
we are testing Gluster 3.3 as an alternative to our current Nexenta based
storage. With the introduction of granular
25 matches
Mail list logo
