Description of problem:
========================
In a distribute-replicate setup, after enabling "uss" and from tried to "cd .snaps" from fuse and nfs mount.
On nfs , "ls -l" returned "Remote I/O Error" . Hence performed "strace ls -l" .
disabled "uss" and once again enabled "uss".
One of the snaps log file was completely filled with the following message:
[2014-07-02 13:15:12.669649] W [glfs-handleops.c:1079:glfs_h_create_from_handle] 0-meta-autoload: inode refresh of 56878e92-e104-48e9-97ef-e21e775627ec failed: No such file or directory
[2014-07-02 13:15:12.669687] E [snapview-server.c:1172:svs_lookup_gfid] 0-rep-snapview-server: failed to do lookup and get the handle on the snapshot (null) (path: <gfid:56878e92-e104-48e9-97ef-e21e775627ec>, gfid: 56878e92-e104-48e9-97ef-e21e775627ec)
Version-Release number of selected component (if applicable):
=============================================================
glusterfs 3.6.0.22 built on Jun 23 2014 10:33:07
How reproducible:
=================
Tried once
Steps to Reproduce:
====================
1.Create a distribute-replicate volume. Start the volume. set the "features.uss" option to "enable"
2. Create nfs mount. Create few files/dirs.
3. Create a snapshot .
4. set the "features.uss" option to "enable"
5. From nfs mount, cd ".snaps" directory.
6. ls -l ".snaps"
7. cd mount
8. disable "features.uss"
9. Create files/dirs.
10. set the "features.uss" option to "enable"
11. ls -l ".snaps"
Actual results:
====================
root@mia [Jul-03-2014-17:05:09] >grep -e "0-rep-snapview-server: failed to do lookup and get the handle on the snapshot (null) " /var/log/glusterfs/snap2-8b4330e3-5a71-4b1a-84bf-455924345d98.log | wc
14752232 309796886 3732314859
Additional Info:
=====================
SOS Reports: http://rhsqe-repo.lab.eng.blr.redhat.com/bugs_necessary_info/1115944/
Log file : http://rhsqe-repo.lab.eng.blr.redhat.com/bugs_necessary_info/1115944/mia_mgmt_node/snap2-8b4330e3-5a71-4b1a-84bf-455924345d98.log
Comment 2Vijaikumar Mallikarjuna
2014-11-21 06:23:00 UTC
*** This bug has been marked as a duplicate of bug 1159173 ***
Comment 3Vijaikumar Mallikarjuna
2016-04-07 03:33:54 UTC
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-2017:2774
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-2017:2774