Hi Atin, Thanks for the reply. I still have some space left on disk I don't know if that is enough though. I don't know what cluster.min-free-disk[1] is for my cluster. Is there a way to find it out? Following are the disk size on my server machine. $ df -h Filesystem Size Used Avail Use% Mounted on /dev/xvda2 5.0G 2.7G 2.1G 58% / tmpfs 869M 0 869M 0% /lib/init/rw udev 839M 36K 839M 1% /dev tmpfs 869M 0 869M 0% /dev/shm /dev/xvda1 107M 15M 87M 15% /mnt/boot none 869M 0 869M 0% /dev/shm /dev/xvdf 20G 6.4G 14G 32% /gluster Also will it be problematic to increase the size of the disk, both / and /gluster, reboot the machine and then start the demon? [1]: http://gluster.org/community/documentation/index.php/Gluster_3.2:_Setting_Volume_Options#cluster.min-free-disk On Mon, Nov 2, 2015 at 10:32 AM, Atin Mukherjee <amukherj@xxxxxxxxxx> wrote: > The following log entry indicates that you are still running out of space. > > [2015-10-31 01:07:04.798509] E > [glusterd-store.c:1150:glusterd_store_handle_retrieve] 0-glusterd: > Unable to retrieve store handle for > /etc/glusterd/vols/ufiles/bricks/(null), error: No such file or directory > > a df output from all your servers can help you to create more space. > > Thanks, > Atin > On 10/31/2015 07:01 AM, Waseem Ahmad wrote: >> Hi all, >> >> Recently / of one of my nodes filled up this caused the glusterd to >> crash. Now when I have increased the size of / and try to restart >> glusterd, it gives me following error. glusterd on all nodes crashed. >> I don't know if crash on all nodes was because of / filled up. Here's >> the output of # glusterd --debug. >> >> https://gist.githubusercontent.com/waseem/1fc7da915a7e9d6119f2/raw/de8658df104040ebcd1c486bd2b9cbd9a56df73b/glusterd-error.txt >> >> What could be wrong? >> >> Regards >> -- Waseem Blog: http://waseem-ahmad.com Twitter: http://twitter.com/_waseem _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
