[Gluster-users] autofs problem

[Craig Carl]

Brent - 
Your data wouldn't need to change or be moved for the upgrade, you just need to make sure that the gluster command in 3.1 supports your volume configuration, it will work for 90% of all possible volume configurations. 

The RHEL/CentOS upgrade guide is here - http://www.gluster.com/community/documentation/index.php/Gluster_3.0_to_3.1_Upgrade_Guide 



Thanks, 

Craig 

-- 
Craig Carl 













Senior Systems Engineer; Gluster, Inc. 
Cell - ( 408) 829-9953 (California, USA) 
Office - ( 408) 770-1884 
Gtalk - craig.carl at gmail.com 
Twitter - @gluster 
Installing Gluster Storage Platform, the movie! 
http://rackerhacker.com/2010/08/11/one-month-with-glusterfs-in-production/ 



From: "Brent A Nelson" <brent at phys.ufl.edu> 
To: "Amar Tumballi" <amar at gluster.com> 
Cc: gluster-users at gluster.org 
Sent: Wednesday, October 20, 2010 12:27:17 PM 
Subject: Re: [Gluster-users] autofs problem 

On Wed, 20 Oct 2010, Amar Tumballi wrote: 

> Brent, 
> 
> Can you please try with 3.1.0 ? (if its a new setup) 
> 
> I remember seeing this issue long back when I was fixing 'autofs' issues 
> with 3.0.x release, and fixing it. Let me recheck it again. 
> 
> Regards, 
> Amar 

It's not a new setup, but I went ahead and created an extremely simple 
Gluster share in 3.0.5, confirmed that it still had the autofs issue, and 
then did the same for a little 3.1.0 test. 

3.1.0 did not have an autofs problem in this quick test, but 3.0.5 did. 
So, it does look like 3.1 includes a fix for this issue. 

This makes me wonder how hard it would be to migrate my existing 3.0 setup 
to 3.1. My volume specs predate volgen, although they are pretty much 
straightforward distributed replicate volumes; would my existing backend 
data be picked up okay if I created fresh 3.1 volumes but used my existing 
backend data areas? Or would there be some extended attributes in the data 
areas that might not match up with the new situation and cause problems? 

Thanks, 

Brent 

> 
> On Wed, Oct 20, 2010 at 1:06 AM, Brent A Nelson <brent at phys.ufl.edu> wrote: 
> 
>> I'm working on replacing my Ubuntu 8.04 desktops with Ubuntu 10.04, but 
>> I've hit a snag. Automount hangs on glusterfs (tried 3.0.4 and 3.0.5) in 
>> the same manner as described on the RedHat Bugzilla: 
>> https://bugzilla.redhat.com/show_bug.cgi?id=603378 
>> 
>> So, it's apparently a problem in Fedora, too. 
>> 
>> It also looks like Phil Packer reported the same issue in February and 
>> perhaps the same issue was also reported by Christopher Nelson in May. 
>> 
>> mount -t glusterfs ... works just fine by hand, but when autofs calls it, 
>> the result is 5 lingering processes: the mount command, the mount.glusterfs 
>> command that it called, a glusterfs command, a zombie glusterfs, and then 
>> another glusterfs. It seems clear that autofs only called the mount command 
>> once, and mount.glusterfs seesmt o have only called glusterfs once, but 
>> glusterfs somehow failed and respawned a couple of times... 
>> 
>> Is there a fix or workaround (other than to not use autofs)? Ubuntu 8.04 
>> doesn't seem to have this issue, although I have had some machines hang up 
>> eventually (with heavy computing/network use), and the symptoms seem to 
>> match a hung-up autofs, so it's possible a similar issue is present but much 
>> more subtle... 
>> 
>> Thanks, 
>> 
>> Brent Nelson 
>> Director of Computing 
>> Dept. of Physics 
>> University of Florida 
>> _______________________________________________ 
>> Gluster-users mailing list 
>> Gluster-users at gluster.org 
>> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users 
>> 
> 
_______________________________________________ 
Gluster-users mailing list 
Gluster-users at gluster.org 
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users