Hi,
I have an odd situation with a dataserver that uses XA space names and how space
usage is being reported.
I export an area named /xrd
We are not using mig or stage options on the export.
I have a named space:
oss.space ATLASDATADISK /xrd_cache_*
At the system level, only files written to /xrd/datadisk should be in the
ATLASDATADISK space.
I have a script that walks the exported directory to discover the files being
stored on the server and record date and size information:
find -L /xrd -type f -fprintf /tmp/xrd_files '%p %T@ %s\n'
If I run 'frm_admin -c /etc/xrootd/xrootd-clustered.cfg audit usage' I get
amounts for claimed and actual bytes used by the various named spaces including
ATLASDATADISK.
The problem is that the amount claimed in the audit output is 20TB (33%) larger
than what I expect by walking the path /xrd/datadisk.
It looks like there are files in /xrd_cache_x/ATLASDATDISK/... that do not have
links in /xrd/datadisk.
What is the correct way to rectify this issue?
I tried to run
frm_admin -c /etc/xrootd/xrootd-clustered.cfg audit space ATLASDATADISK
0 problems found; 0 fixed.
Space ATLASDATADISK has 0 files with 0 bytes in use (0 unreachable).
Should I run an audit names?
Should the audit invocation look like:
... audit name /xrd/datadisk
?
Thanks for any insights,
Patrick
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1
