Bug 1302751 - USS: Huge logging in samba client logs while accessing .snaps folder from cifs client
USS: Huge logging in samba client logs while accessing .snaps folder from cif...
Status: NEW
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: samba (Show other bugs)
3.1
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: rhs-smb@redhat.com
storage-qa-internal@redhat.com
: ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-01-28 09:17 EST by surabhi
Modified: 2017-03-25 12:26 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description surabhi 2016-01-28 09:17:48 EST
Description of problem:

While running automated TC's for USS :
1.Enable USS on volume, list snaps under .snaps dir"
2.start and stop snapd
3.start and stop snapd when USS is enabled/disabled"

Version-Release number of selected component (if applicable):
glusterfs-libs-3.7.5-17.el7rhgs.x86_64
glusterfs-rdma-3.7.5-17.el7rhgs.x86_64
glusterfs-cli-3.7.5-17.el7rhgs.x86_64
samba-vfs-glusterfs-4.2.4-12.el7rhgs.x86_64
glusterfs-client-xlators-3.7.5-17.el7rhgs.x86_64
glusterfs-server-3.7.5-17.el7rhgs.x86_64
glusterfs-api-3.7.5-17.el7rhgs.x86_64
glusterfs-geo-replication-3.7.5-17.el7rhgs.x86_64
glusterfs-fuse-3.7.5-17.el7rhgs.x86_64
glusterfs-3.7.5-17.el7rhgs.x86_64


How reproducible:
Always

Steps to Reproduce:
1.Do setup required for USS
2.Mount the volume on cifs client , create I/O's , take snapshots
3.enable USS
4.Activate snapshot
5.cd .snaps on cifs mount

Actual results:
**********************
Huge logging in samba client logs.

Expected results:
This much huge logging should not be there.

Additional info:

Note You need to log in before you can comment on or make changes to this bug.