| vzctl stop kills glusterfs? [message #37872] |
Thu, 29 October 2009 10:26  |
kiskele
Messages: 2
Registered: October 2009
|
Junior Member |
|
|
I have a glusterfs mount outside:
| Quote: | /etc/glusterfs/glusterfs.vol on /media/glusterfs type fuse.glusterfs (rw,allow_other,default_permissions,max_read=131072)
|
I made a mount and umount script:
| Quote: |
/etc/vz/conf/126.mount:
#!/bin/sh
source /etc/vz/vz.conf
source ${VE_CONFFILE}
mount --bind /media/glusterfs/var/www ${VE_ROOT}/var/www
/etc/vz/conf/126.umount:
#!/bin/sh
source /etc/vz/vz.conf
source ${VE_CONFFILE}
umount ${VE_ROOT}/var/www
exit 0
|
vzctl start 126 was ok.
vzctl stop 126 says:
| Quote: |
Stopping container ...
Container was stopped
umount: /media/glusterfs/var/www: Transport endpoint is not connected
umount: /var/lib/vz/root/126/var/www: not mounted
umount: /media/glusterfs/var/www: Transport endpoint is not connected
umount: /var/lib/vz/root/126/var/www: not mounted
Container is unmounted
|
I started glusterfs in debug mode, and it said:
| Quote: |
[2009-10-29 11:19:09] N [fuse-bridge.c:2544:fuse_thread_proc] fuse: unmounting /media/glusterfs/
[2009-10-29 11:19:09] W [glusterfsd.c:928:cleanup_and_exit] glusterfs: shutting down
|
but mount still exist. Trying to list content said "Transport endpoint is not connected".
Which part of OpenVZ kills my glusterfs and how can I fix it?
linux-2.6.18-14-fza-686, fuse-2.7.4glfs11, glusterfs-2.0.7
[Updated on: Thu, 29 October 2009 10:31] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
