Release 3.0.x has the same behavior what you describe here, which is not
really an issue. Please verify if some other component in your system
changed (kernel or fuse kernel module) which has changed the behavior for
you.

Avati

On Thu, Dec 2, 2010 at 7:29 PM, Samuel Hassine <sam...@hassine.fr> wrote:

> Hi all,
>
>
>
> GlusterFS partition automatically shutdown when umounting a binded mount
> point
>
> with "-f" option (without it works).
>
>
>
> How to reproduce:
>
>
>
> mounted Gluster partition on /gluster (any config):
>
>
>
> df: localhost:/gluster        4.5T  100G  4.4T   3% /gluster
>
> mount: localhost:/gluster on /gluster type fuse.glusterfs
>
> (rw,allow_other,default_permissions,max_read=131072)
>
>
>
> commands:
>
>
>
> mkdir /test
>
> mount -n --bind /gluster /test
>
> ls /test (verify you have the Gluster)
>
>
>
> and:
>
>
>
> umount -f /test
>
>
>
> ===>
>
>
>
> df: `/gluster': Transport endpoint is not connected
>
> [2010-12-02 14:48:56.38309] I [fuse-bridge.c:3138:fuse_thread_proc] fuse:
>
> unmounting /gluster
>
> [2010-12-02 14:48:56.38364] I [glusterfsd.c:672:cleanup_and_exit]
> glusterfsd:
>
> shutting down
>
>
>
> Before 3.1.x I did not have this bug.
>
>
>
> Regards.
>
> Sam
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users@gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>
>
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users

Reply via email to