[Bugs] [Bug 1359020] New: [Bitrot]: Sticky bit files considered and skipped by the scrubber, instead of getting ignored.

bugzilla at redhat.com bugzilla at redhat.com
Fri Jul 22 06:17:03 UTC 2016


https://bugzilla.redhat.com/show_bug.cgi?id=1359020

            Bug ID: 1359020
           Summary: [Bitrot]: Sticky bit files considered and skipped by
                    the scrubber, instead of getting ignored.
           Product: GlusterFS
           Version: 3.8.1
         Component: bitrot
          Keywords: ZStream
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: khiremat at redhat.com
                CC: bugs at gluster.org, khiremat at redhat.com,
                    sanandpa at redhat.com
        Depends On: 1342459, 1355706, 1359017
      Docs Contact: bugs at gluster.org



+++ This bug was initially created as a clone of Bug #1359017 +++

+++ This bug was initially created as a clone of Bug #1355706 +++

+++ This bug was initially created as a clone of Bug #1342459 +++

Description of problem:
=======================
If we have sticky bit files present in a distribute replicate volume, then they
get displayed as 'skipped' in the scrub status output. Considering that the
actual file would have anyways gotten considered, the scrubber should ideally
be ignoring all T files.


Version-Release number of selected component (if applicable):
==========================================================


How reproducible:
================
Reporting the first occurrence.


Steps to Reproduce:
===================
1. Have a 4node cluster, with n*2 distribute replicate volume.
2. Create files from the mountpoint
3. Create a scenario such that sticky bit files are created (say, kill a brick
process, and do creates)
4. Validate the scrub status output

Actual results:
================
Step4 shows a number>0 in the field 'Files skipped' in scrub status output.

Expected results:
==================
Step4 should not show any files as skipped, as there is no open FD while the
scrubber is doing its run.


[[root at dhcp46-187 ~]# 
[root at dhcp46-187 ~]# 
[root at dhcp46-187 ~]# gluster v list
disp
distrep2
distrep3
gluster_shared_storage
mm
[root at dhcp46-187 ~]# 
[root at dhcp46-187 ~]# 
[root at dhcp46-187 ~]# gluster v info distrep2

Volume Name: distrep2
Type: Distributed-Replicate
Volume ID: a40e89f0-02dd-4fa7-8687-afe0f092ae80
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: 10.70.47.188:/brick/brick1/distrep2
Brick2: 10.70.46.215:/brick/brick1/distrep2
Brick3: 10.70.46.187:/brick/brick1/distrep2
Brick4: 10.70.46.193:/brick/brick1/distrep2
Options Reconfigured:
cluster.self-heal-daemon: enable
performance.readdir-ahead: on
features.bitrot: on
features.scrub: Active
features.scrub-freq: hourly
[root at dhcp46-187 ~]# 
[root at dhcp46-187 ~]# 
[root at dhcp46-187 ~]# 
[root at dhcp46-187 ~]# gluster v bitrot distrep2 scrub status

Volume name : distrep2

State of scrub: Active

Scrub impact: lazy

Scrub frequency: hourly

Bitrot error log location: /var/log/glusterfs/bitd.log

Scrubber error log location: /var/log/glusterfs/scrub.log


=========================================================

Node: localhost

Number of Scrubbed files: 9

Number of Skipped files: 1

Last completed scrub time: 2016-06-03 10:21:46

Duration of last scrub (D:M:H:M:S): 0:0:0:43

Error count: 0


=========================================================

Node: 10.70.46.193

Number of Scrubbed files: 9

Number of Skipped files: 1

Last completed scrub time: 2016-06-03 10:21:45

Duration of last scrub (D:M:H:M:S): 0:0:0:42

Error count: 0


=========================================================

Node: dhcp47-188.lab.eng.blr.redhat.com

Number of Scrubbed files: 13

Number of Skipped files: 0

Last completed scrub time: 2016-06-03 10:21:50

Duration of last scrub (D:M:H:M:S): 0:0:0:46

Error count: 0


=========================================================

Node: 10.70.46.215

Number of Scrubbed files: 13

Number of Skipped files: 0

Last completed scrub time: 2016-06-03 10:21:49

Duration of last scrub (D:M:H:M:S): 0:0:0:46

Error count: 0

=========================================================

[root at dhcp46-187 ~]# 
[root at dhcp46-187 ~]# 
[root at dhcp46-187 ~]# cd /brick/brick1/distrep2/dir1/dir2/dir3/dir4/dir5/
[root at dhcp46-187 dir5]# ls -l
total 32
---------T. 2 root root 20 Jun  3 11:59 file1_ln
-rw-r--r--. 2 root root 22 Jun  3 11:25 test1
-rw-r--r--. 2 root root 22 Jun  3 11:25 test2
-rw-r--r--. 2 root root 22 Jun  3 11:25 test4
[root at dhcp46-187 dir5]# 
[root at dhcp46-187 dir5]#


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1342459
[Bug 1342459] [Bitrot]: Sticky bit files considered and skipped by the
scrubber, instead of getting ignored.
https://bugzilla.redhat.com/show_bug.cgi?id=1355706
[Bug 1355706] [Bitrot]: Sticky bit files considered and skipped by the
scrubber, instead of getting ignored.
https://bugzilla.redhat.com/show_bug.cgi?id=1359017
[Bug 1359017] [Bitrot]: Sticky bit files considered and skipped by the
scrubber, instead of getting ignored.
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the Docs Contact for the bug.


More information about the Bugs mailing list