Hide Forgot
PATCH: http://patches.gluster.com/patch/4790 in master (Volume stop/start fails sometimes)
gluster> volume start new Starting volume new has been unsuccessful Volume name new, brick: 192.168.1.131:/export/dir1, path /export/dir1 is not present after ends are up backend gluster> volume start new Starting volume new has been unsuccessful Volume new already started root@shishirng-laptop:/home/shishirng# gluster volume stop new Stopping volume will make its data inaccessible. Do you want to Continue? (y/n) y Stopping volume new has been unsuccessful gluster> volume info Volume Name: new Type: Replicate Status: Started <----state is started Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: 192.168.1.131:/export/dir1 Brick2: 192.168.1.131:/export/dir2 even force fails: gluster> volume stop new force Stopping volume will make its data inaccessible. Do you want to Continue? (y/n) y Stopping volume new has been successful gluster> volume info Volume Name: new Type: Replicate Status: Started Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: 192.168.1.131:/export/dir1 Brick2: 192.168.1.131:/export/dir2 log msg: [2010-09-15 12:26:27.215746] I [glusterd-op-sm.c:2730:glusterd_op_stop_volume] : About to stop glusterfs for brick 192.168.1.131:/export/dir1 [2010-09-15 12:26:27.215809] E [glusterd-utils.c:868:glusterd_volume_stop_glusterfs] : Unable to open pidfile: /etc/glusterd/vols/new/run/192.168.1.131-export-dir1.pid The file does not exist