3.0.6 also appears to have fixed the autofs problem.
Thanks,
Brent
On Wed, 20 Oct 2010, Brent A Nelson wrote:
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 <[email protected]> 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
[email protected]
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
[email protected]
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
