Red Hat Bugzilla – Bug 1158898
[USS]: creating file/directories under .snaps shows wrong error message
Last modified: 2016-09-17 09:03:18 EDT
Description of problem: ======================= When an attempt is made to create file/directories inside .snaps, it fails with wrong error message as "Stale file handle". It should fail with "Read only file system" Version-Release number of selected component (if applicable): ============================================================= glusterfs-3.6.0.30-1.el6rhs.x86_64 How reproducible: ================== always Steps to Reproduce: =================== 1. Enable uss on the volume 2. Cd to .snaps from the client Actual results: =============== [root@wingo .snaps]# mkdir a mkdir: cannot create directory `a': Stale file handle [root@wingo .snaps]# touch a touch: cannot touch `a': Stale file handle [root@wingo .snaps]# Expected results: ================= [root@wingo .snaps]# mkdir a mkdir: cannot create directory `a': Read-only file system [root@wingo .snaps]# touch a touch: cannot touch `a': Read-only file system [root@wingo .snaps]#
Patch submitted: https://code.engineering.redhat.com/gerrit/36478
Verified with build: glusterfs-3.6.0.33-1.el6.x86_64 From Fuse: ---------- [root@wingo .snaps]# mount | grep "/mnt/vol0" inception.lab.eng.blr.redhat.com:/vol0 on /mnt/vol0 type fuse.glusterfs (rw,default_permissions,allow_other,max_read=131072) [root@wingo .snaps]# [root@wingo .snaps]# pwd /mnt/vol0/.snaps [root@wingo .snaps]# mkdir temp mkdir: cannot create directory `temp': Read-only file system [root@wingo .snaps]# From Fuse: ---------- [root@wingo .snaps]# mount | grep "/mnt/nvol0" inception.lab.eng.blr.redhat.com:/vol0 on /mnt/nvol0 type nfs (rw,vers=3) [root@wingo .snaps]# cd /mnt/nvol0/.snaps [root@wingo .snaps]# pwd /mnt/nvol0/.snaps [root@wingo .snaps]# mkdir temp1 mkdir: cannot create directory `temp1': Read-only file system [root@wingo .snaps]# 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://rhn.redhat.com/errata/RHBA-2015-0038.html