Description of problem: statfs is not handled in user-serviceable snaps Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. getconf NAME_MAX /mnt/.snaps/<snap-name> 2. 3. Actual results: getconf fails Expected results: getconf should not fail Additional info:
Avra, I see this bug in the known issues tracker bug for 3.0.3. Can you please change the doc type field to known issue and fill out the doc text?
Hi Avra, Can you please review the edited doc text for technical accuracy and sign off?
Looks good Pavithra. Thanks.
Fixed with http://review.gluster.org/#/c/10356/ and http://review.gluster.org/#/c/10358/
[root@client glusterfs]# ./statvfs /mnt/glusterfs/.snaps f_bsize (block size): 1702057286 f_frsize (fragment size): 131072 f_blocks (size of fs in f_frsize units): 819200 f_bfree (free blocks): 819199 f_bavail free blocks for unprivileged users): 819199 f_files (inodes): 193673088 f_ffree (free inodes): 193659676 f_favail (free inodes for unprivileged users): 0 f_fsid (file system ID): 255 f_flag (mount flags): 131072 f_namemax (maximum filename length)4128 [root@client glusterfs]# ./statvfs /mnt/glusterfs/.snaps/snap1_GMT-2015.07.06-06.26.03/ f_bsize (block size): 1702057286 f_frsize (fragment size): 131072 f_blocks (size of fs in f_frsize units): 819200 f_bfree (free blocks): 819200 f_bavail free blocks for unprivileged users): 819200 f_files (inodes): 193673088 f_ffree (free inodes): 193614396 f_favail (free inodes for unprivileged users): 0 f_fsid (file system ID): 255 f_flag (mount flags): 131072 [root@client .snaps]# getconf NAME_MAX /mnt/glusterfs/.snaps/ 255 [root@client glusterfs]# getconf NAME_MAX /mnt/glusterfs/.snaps/snap1_GMT-2015.07.06-06.26.03 255 Bug verified on build glusterfs-3.7.1-7.el6rhs.x86_64
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://rhn.redhat.com/errata/RHSA-2015-1495.html