Yeah, that's quiet annoying on 3.3 I've run into the same problem when trying to re-create a volume made of the same disks that I couldn't get rid of even using these commands, so I ended up replacing the physical disks and re-creating the partition. Even when you do a Delete on the volume it seems to run into the same trouble. Fernando From: Simon Blackstein [mailto:simon at blackstein.com] Sent: 26 June 2012 18:01 To: Anand Avati Cc: Fernando Frediani (Qube); gluster-users at gluster.org Subject: Re: Gluster 3.3.0 and VMware ESXi 5 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 the directory... lots of changes in this version to watch out for :( 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 Many Rgds, Simon On Tue, Jun 26, 2012 at 8:28 AM, Anand Avati <anand.avati at gmail.com<mailto:anand.avati at gmail.com>> wrote: Is this at the same 'time' as before (at the time for VM boot), or does it actually progress a little more (i.e, "start booting") and then throw up? It will be helpful if we move this discussion to bugzilla and you provide trace logs. Avati On Tue, Jun 26, 2012 at 7:59 AM, Simon Blackstein <simon at blackstein.com<mailto:simon at blackstein.com>> wrote: Hi Avati, Thanks. I just tried a recompile (I'd installed from RPM before) and brought up the volume again. I now get a similar but different message: An unexpected error was received from the ESX host while powering on VM vm-26944. Failed to power on VM. Could not power on VM : Not found. Failed to create swap file '/gfs/gfs-test1/./gfs-test1-d27c6ac2.vswp' : Not found I only modified the first brick node which is where I'm pointing the ESXi server as NFS client. Do I need to modify all nodes like this? Many Thanks! Simon On Tue, Jun 26, 2012 at 4:14 AM, Anand Avati <anand.avati at gmail.com<mailto:anand.avati at gmail.com>> wrote: Fernando, Yes, to try the patch you need to install from source. We will include the patch in the next release if you need RPMs. Avati On Tue, Jun 26, 2012 at 3:02 AM, Fernando Frediani (Qube) <fernando.frediani at qubenet.net<mailto:fernando.frediani at qubenet.net>> wrote: Hi Avati, How I suppose to apply the patch if I have installed the RPM version ? Should I have a compiled from source installed instead ? Regards, Fernando From: gluster-users-bounces at gluster.org<mailto:gluster-users-bounces at gluster.org> [mailto:gluster-users-bounces at gluster.org<mailto:gluster-users-bounces at gluster.org>] On Behalf Of Anand Avati Sent: 26 June 2012 04:00 To: Simon Cc: gluster-users at gluster.org<mailto:gluster-users at gluster.org> Subject: Re: 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 <simon at blackstein.com<mailto:simon at 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 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 directory: 0 (No such file or directory). Check if the directory has been deleted or unmounted. Unable to retrieve the current working directory: 0 (No such file or directory). Check if the directory has been deleted or unmounted. Is GlusterFS supported against VMware or should I be looking somewhere else? _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org<mailto:Gluster-users at gluster.org> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gluster.org/pipermail/gluster-users/attachments/20120626/37de0457/attachment-0001.htm>
