Does anyone have suggestions what may be causing this?
One FST only is logging xrdlog.fst messages for multiple fsids which do not exist, e.g
200214 21:39:13 time=1581712753.307294 func=publishFsStatistics level=WARN logid=static… unit=fst@warp-ornl-cern-07.ornl.gov:1095 tid=00007f3264890700 source=Publish:423 tident= sec=(null) uid=99 gid=99 name=- geo=“” asked to publish statistics for filesystem with fsid=0
200214 21:39:13 time=1581712753.307310 func=Publish level=ERROR logid=static… unit=fst@warp-ornl-cern-07.ornl.gov:1095 tid=00007f3264890700 source=Publish:480 tident= sec=(null) uid=99 gid=99 name=- geo=“” cannot set net parameters on filesystem /fsidmnt/7179
However, no such fsid has been registered to the mgm
[root@ornl-eos-01 ~]# grep ‘fsidmnt/7179’ /var/eos/config/ornl-eos-01.ornl.gov/default.eoscf
[root@ornl-eos-01 ~]# eos fs status 7179
error: cannot find filesystem - no filesystem with fsid=7179
On the FST side, there is no /fsidmnt/7179 mounted nor any /var/eos/md/fmd.7179.LevelDB/
Cheers,
Pete