gluster-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gluster-devel] Glusterfs not mounting correctly during boot under R


From: Ioannis Aslanidis
Subject: Re: [Gluster-devel] Glusterfs not mounting correctly during boot under RHEL 5.2
Date: Wed, 05 Nov 2008 09:58:18 +0100
User-agent: Thunderbird 2.0.0.17 (X11/20081012)


Gordan Bobic wrote:
> All sorts of problems still come up regularly, but they get fixed pretty 
> quickly. I suggest you try the current release 1.3.12. It's still not 
> perfect, but it's a lot less buggy than 1.3.8pre6.

Can you point me at the particular fix for my problem in the current
version? Advising an upgrade without being sure that it will fix the
problem is not a valid option. Which feature/patch may fix my problem?

> 
> As an aside, are you sure the rest of the setup is the same (volume specs, 
> firewall rules, etc.). If you are using the same gluster binaries on both, 
> your problem is most likely related to an OS configuration issue. Have you 
> verified that client/server daemons are running? Is fuse module loaded on the 
> client?

I know the problem is probably OS related, this is why I am asking if
someone experienced this before on RHEL 5.2. The firewall rules look
fine. Both the client and the server are running.

The fuse module is definitely loaded on the client after fixing some
SELinux problems and there are no more SELinux audits that report
problems, so I am stuck there.

Regards,

Ioannis

> 
> Gordan
> 
> -----Original Message-----
> From: "Ioannis Aslanidis" <address@hidden>
> To: "Gluster Devel" <address@hidden>
> Sent: 04/11/08 15:57
> Subject: Re: [Gluster-devel] Glusterfs not mounting correctly during boot     
> under   RHEL 5.2
> 
> Didn't anyone experience this problem before? Can anyone help?
> 
> Ioannis Aslanidis wrote:
>> Hello,
>>
>> I experience problems with the glusterfs client under RHEL 5.2. The
>> problem is that, while booting, the partition does not get properly
>> mounted. It gives several 'Transport endpoint is not connected' for a
>> minute or so before working properly.
>>
>> I have exactly the same client setup under Fedora and it works correctly.
>>
>> The server is the same for both. Please, do not propose to upgrade
>> glusterfs unless you are 100% sure that it will fix my problem. As I
>> said, the exact setup works under Fedora.
>>
>> I saw several SELinux denegations, which I fixed. Now I see no more
>> SELinux denegations any more.
>>
>> Server: glusterfs 1.3.8pre6 built on Apr 23 2008 04:34:21
>> Client on Fedora: glusterfs 1.3.8pre6 built on Apr 23 2008 04:31:19
>> Client on RHEL: glusterfs 1.3.8pre6 built on Sep  8 2008 14:22:53
>>
>> The message log:
>>
>> 2008-11-03 17:10:46 E [client-protocol.c:4405:client_lookup_cbk]
>> filedata: no proper reply from server, returning ENOTCONN
>> 2008-11-03 17:10:46 E [fuse-bridge.c:459:fuse_entry_cbk] glusterfs-fuse:
>> 2: (34) / => -1 (107)
>> 2008-11-03 17:10:46 E [client-protocol.c:4405:client_lookup_cbk]
>> filedata: no proper reply from server, returning ENOTCONN
>> 2008-11-03 17:10:46 E [fuse-bridge.c:459:fuse_entry_cbk] glusterfs-fuse:
>> 2: (34) / => -1 (107)
>> 2008-11-03 17:10:49 E [client-protocol.c:4405:client_lookup_cbk]
>> filedata: no proper reply from server, returning ENOTCONN
>> 2008-11-03 17:10:49 E [fuse-bridge.c:459:fuse_entry_cbk] glusterfs-fuse:
>> 3: (34) / => -1 (107)
>> 2008-11-03 17:10:49 E [client-protocol.c:4405:client_lookup_cbk]
>> filedata: no proper reply from server, returning ENOTCONN
>> 2008-11-03 17:10:49 E [fuse-bridge.c:459:fuse_entry_cbk] glusterfs-fuse:
>> 3: (34) / => -1 (107)
>>
>>
>> Thanks for the prompt reply.
>>
>> Regards,
>>
>> Ioannis
>>
>>
>> -----------------------
> 
> 
> _______________________________________________
> Gluster-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/gluster-devel

Attachment: iaslanidis.vcf
Description: Vcard

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]