Fsck : settings, communication between managers and FSTs

13

Hi Elvin,

Thank you.

OK, I am following this attribute user.eos.timestamp and I can see that the test file that I have created is rescanned after scaninterval:

210511 08:46:08 time=1620715568.945736 func=RunDiskScan level=NOTE logid=8bbc1f08-aefe-11eb-8339-003048de1e44 unit=fst@naneostest01.in2p3.fr:1095 tid=00007fc0fdfe8700 source=ScanDir:504 tident= sec= uid=0 gid=0 name= geo=“” [ScanDir] Directory: /data2 files=3 scanduration=0 [s] scansize=23 [Bytes] [ 2.3e-05 MB ] scannedfiles=1 corruptedfiles=0 hwcorrupted=0 skippedfiles=0

However, it looks like that the minor modification (changed 1 byte) that I made to the test file goes unnoticed. The checksum has changed. It was 58a806f2 before, it is now 59d40701:

[root@naneostest01 ~]# /opt/eos/xrootd/bin/xrdadler32 /data2/00000000/00000139
59d40701 /data2/00000000/00000139

[root@naneostest01 ~]# eos-leveldb-inspect --dbpath /var/eos/md/fmd.0004.LevelDB/ --fid 313
fxid=139 id=313 cid=16 fsid=4 ctime=1620649219 ctime_ns=491829528 mtime=1620649217 mtime_ns=340096000 atime=1620649217 atime_ns=340096000 size=23 disksize=23 mgmsize=23 lid=0x100002 uid=99 gid=99 filecxerror=0x0 blockcxerror=0x0 layouterror=0x0 checksum=58a806f2 diskchecksum=none mgmchecksum=58a806f2 locations=4

[root@naneostest01 ~]# getfattr -d /data2/00000000/00000139
getfattr: Removing leading ‘/’ from absolute path names
# file: data2/00000000/00000139
user.XrdCks.adler32=0sYWRsZXIzMgAAAAAAAAAAAAAAAABgmTcwAAAAAQAAAARZ1AcBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
user.eos.blockcxerror=“0”
user.eos.filecxerror=“0”
user.eos.timestamp=“1620715273”

What I do not understand:

  1. the fact that this change of checksum is not reported
  2. the field diskchecksum being at none in LevelDB
  3. the stange value for user.XrdCks.adler32 in the file attributes

Sorry for splitting hair

JM