Description of problem: When assert_on_child_down is enabled, glusterfs process exits without providing an opportunity to do cleanup before exiting. This needs to be corrected. Version-Release number of selected component (if applicable): 3.2.5 How reproducible: Always Steps to Reproduce: 1. Enable assert_on_child_down in dht 2. Bring a brick down Actual results: A stale client mount is seen Expected results: Stale client mount should not be seen Additional info:
CHANGE: http://review.gluster.com/2682 (cluster/dht: Exit clean when assert_no_child_down is enabled) merged in release-3.2 by Anand Avati (avati)
1. Created a distribute volume with 3 bricks 2. mounted using the command "/opt/glusterfs/3.2.6qa3/sbin/glusterfs --log-level=INFO --xlator-option=dist*.assert-no-child-down=yes --volfile-id=/dist --volfile-server=10.1.11.117 /mnt" 3. cd /mnt 4. killed one of the brick 5. cd / 6. client was automatically unmounted Marking as verified
CHANGE: http://review.gluster.com/2664 (cluster/dht: Exit clean when assert_no_child_down is enabled) merged in master by Vijay Bellur (vijay)