Description of problem:
nfs.log getting filled with these logs,
[2014-09-04 01:40:27.517380] I [dht-common.c:1828:dht_lookup_cbk] 0-dist-rep-dht: Entry /run16165/fileop_L1_8/fileop_L1_8_L2_14/fileop_dir_8_14_29 missing on subvol dist-rep-replicate-5
[2014-09-04 01:40:27.520240] I [dht-common.c:1085:dht_lookup_everywhere_done] 0-dist-rep-dht: STATUS: hashed_subvol dist-rep-replicate-5 cached_subvol null
[2014-09-04 01:40:27.533708] I [dht-common.c:1828:dht_lookup_cbk] 0-dist-rep-dht: Entry /run16165/fileop_L1_8/fileop_L1_8_L2_15 missing on subvol dist-rep-replicate-2
[2014-09-04 01:40:27.535634] I [dht-common.c:1085:dht_lookup_everywhere_done] 0-dist-rep-dht: STATUS: hashed_subvol dist-rep-replicate-2 cached_subvol null
[2014-09-04 01:40:27.550821] I [dht-common.c:1828:dht_lookup_cbk] 0-dist-rep-dht: Entry /run16165/fileop_L1_8/fileop_L1_8_L2_15/fileop_dir_8_15_0 missing on subvol dist-rep-replicate-5
[2014-09-04 01:40:27.553221] I [dht-common.c:1085:dht_lookup_everywhere_done] 0-dist-rep-dht: STATUS: hashed_subvol dist-rep-replicate-5 cached_subvol null
[2014-09-04 01:40:27.575100] I [dht-common.c:1828:dht_lookup_cbk] 0-dist-rep-dht: Entry /run16165/fileop_L1_8/fileop_L1_8_L2_15/fileop_dir_8_15_1 missing on subvol dist-rep-replicate-0
[2014-09-04 01:40:27.576977] I [dht-common.c:1085:dht_lookup_everywhere_done] 0-dist-rep-dht: STATUS: hashed_subvol dist-rep-replicate-0 cached_subvol null
Version-Release number of selected component (if applicable):
glusterfs-3.6.0.28-1.el6rhs.x86_64
How reproducible:
happen to be regularly seen on the above mentioned build
Steps to Reproduce:
1. create a 6x2 volume
2. start the volume
3. mount the volume over nfs
4. start untar of kernel on mount-point
Actual results:
nfs.log getting filled with the above mentioned messages
Expected results:
Not expecting so many messages
Additional info:
Using glusterfs-3.6.0.29-1, I create a 6x2 volume and mounted it via NFS. I then did a kernel untar on the mount point. The NFS log file did not get filled with the DHT info logs as mentioned in the bug report.
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.
http://rhn.redhat.com/errata/RHBA-2014-1315.html
Comment 9Nithya Balachandran
2014-11-06 07:43:55 UTC
*** Bug 1156624 has been marked as a duplicate of this bug. ***