Description of problem: On a gluster client, if we try to mount volume when /var is filled completely FUSE mount fails with: ################################################################################ # 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) 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 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) 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. Version-Release number of selected component (if applicable): glusterfs-3.12.2-45 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.
> # 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? The reason this is giving a generic 'Mount failed' log at the end is because when the process fails, it fails with -1, and we are not having a tool in bash to log the error message itself. Hence we believe the output is good enough.
Kshithij, With the above explanation, I am inclined towards closing the bug as WONTFIX.
> > # 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.
https://review.gluster.org/22346
Tested with the following : 1. glusterfs-server-6.0-23.el7rhgs.x86_64 2.3.10.0-1062.7.1.el7.x86_64 The steps to reproduce mentioned in description were followed and the following observations were seen:- 1. [root@dhcp46-69 log]# df -Th Filesystem Type Size Used Avail Use% Mounted on devtmpfs devtmpfs 16G 0 16G 0% /dev tmpfs tmpfs 16G 0 16G 0% /dev/shm tmpfs tmpfs 16G 9.0M 16G 1% /run tmpfs tmpfs 16G 0 16G 0% /sys/fs/cgroup /dev/sda1 xfs 100G 1.8G 99G 2% / /dev/sdb1 xfs 200G 200G 100K 100% /var tmpfs tmpfs 3.2G 0 3.2G 0% /run/user/0 The /var/log is filled and volume was mounted on client . Following error messages were seen :- [root@dhcp46-69 mnt]# mount -t glusterfs 10.70.46.182:/vol1 /mnt/vol1 ERROR: failed to create logfile "/var/log/glusterfs/mnt-vol1.log" (No space left on device) ERROR: failed to open logfile /var/log/glusterfs/mnt-vol1.log Mounting glusterfs on /mnt/vol1 failed. The changes were done. Hence moving the bug to verified state.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0288