I have some GlusterFS(Version 3.7.11) volumes created and started, after some test, I stopped hand deleted the volumes, but they are still remain in the GlusterFS servers.
For example, I have 3 servers, and bricks saved under /gfs:
[vagrant@gfs-server-2 ~]$ sudo gluster volume create test-vol gfs-server-1:/gfs/test-vol gfs-server-2:/gfs/test-vol gfs-server-3:/gfs/test-vol force
volume create: test-vol: success: please start the volume to access data
[vagrant@gfs-server-2 ~]$ sudo gluster volume start test-vol
volume start: test-vol: success
[vagrant@gfs-server-2 ~]$ mkdir /tmp/test
[vagrant@gfs-server-2 ~]$ sudo mount -t glusterfs gfs-server-1:/test-vol /tmp/test
[vagrant@gfs-server-2 ~]$ sudo touch /tmp/test/`date +%s`.txt
[vagrant@gfs-server-2 ~]$ sudo touch /tmp/test/`date +%s`.txt
[vagrant@gfs-server-2 ~]$ sudo touch /tmp/test/`date +%s`.txt
[vagrant@gfs-server-2 ~]$ sudo touch /tmp/test/`date +%s`.txt
[vagrant@gfs-server-2 ~]$ sudo ls /tmp/test/
1469617442.txt 1469617446.txt 1469617447.txt 1469617449.txt
[vagrant@gfs-server-2 ~]$ ls /gfs/test-vol/
1469617449.txt
[vagrant@gfs-server-2 ~]$ sudo umount /tmp/test
After delete the volume, I can still see the files remain in the GlusterFS servers:
[vagrant@gfs-server-2 ~]$ sudo gluster volume stop test-vol
Stopping volume will make its data inaccessible. Do you want to continue? (y/n) y
volume stop: test-vol: success
[vagrant@gfs-server-2 ~]$ sudo gluster volume delete test-vol
Deleting volume will erase all information about the volume. Do you want to continue? (y/n) y
volume delete: test-vol: success
[vagrant@gfs-server-2 ~]$ ls /gfs/test-vol/
1469617449.txt
Lists the clients connected to the volume. gluster volume status volume_name mem. Lists the memory usage and memory pool details for each brick in the volume. gluster volume status volume_name inode.
Rebalancing Volume to Fix Layout Changes The command gluster volume rebalance <volname> fix-layout start will fix the layout information so that the files can be created on the newly added bricks. When this command is issued, all the file stat information which is already cached will get revalidated.
GlusterFS volumes present a POSIX-compliant filesystem and are comprised of one or more "bricks" across one or more nodes in their cluster. A brick is just a directory on a given storage node and is typically the mount point for a block storage device.
gluster volume delete
does not delete the data from the back-end, you would need to manually delete them from the bricks. (rm -rf /gfs/test-vol/)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With