This bug was initially created as a copy of Bug #1685406


Description of problem:
On a gluster client, if we try to mount volume when /var is filled completely FUSE mount fails with:
################################################################################
# mount.glusterfs my-node.redhat.com:/testvol_replicated/ bug/
ERROR: failed to create logfile "/var/log/glusterfs/bug-.log" (No space left on device)
ERROR: failed to open logfile /var/log/glusterfs/bug-.log
Mount failed. Please check the log file for more details.
################################################################################

Instead of which a proper error message should be displayed like:
################################################################################
# mount.glusterfs my-node.redhat.com:/testvol_replicated/ bug/
ERROR: failed to create logfile "/var/log/glusterfs/bug-.log" (No space left on device)
ERROR: failed to open logfile /var/log/glusterfs/bug-.log
Mount failed as no space left on device please free disk space. 
################################################################################
As the present error message is misleading.


How reproducible:
1/1

Steps to Reproduce:
1. Create one volume of any type and start it. 
2. On the client node fill /var/log using fallocate.
3. Try to mount the volume on the client.



--- Discussions in above bug ---

> > # mount.glusterfs dhcp35-137.lab.eng.blr.redhat.com:/testvol_replicated/ bug/
> > ERROR: failed to create logfile "/var/log/glusterfs/bug-.log" (No space left on device)
> 
> 
> Doesn't the above line capture the 'issue' at hand?


In that case I would not want the error message "Mount failed. Please check the log file for more details." to be displayed at all. Because it would create confusion for when read by the user, as log-file creation itself failed.