Ran xcp scan -du on a 30TB NFS share, which would approximately have 120million files.
xcp scan took about 6 hours to scan 104million files, but after that for next 10hrs it was in same state but i see continuous "xcp re-opener" and "mod time chnaged, reading anyway" warning/info event in the logs.
im using 1.7 xcp version, attaching the xcp logs for reference.
Hi, Since XCP scan was aborted manually. I suggest to please re-run the xcp scan with -stats -showmem as suggested earlier, it would help. I only could see there is possibility of issue with the NW and could not see issue with XCP from the given log. Regards Ashutosh
As suggested I will try out the option you suggested and feedback.
In the meantime, I would like to highlight one point --> if you could see the xcp logs, my scan start time is: 2021-06-20 17:14 and by 2021-06-20 22:47 around 103M files scanned, till this time frame there were no warning events in the logs, exactly at 2021-06-20 22:48 I see a warning event for the CATALOG INDEX 100.65.233.221:/Infibeam2/catalog/indexes/200601_1/200601_1.index, i see continuous warnings for this index, currently we are uncertain why catalog index was experiencing an issue. (May be becoz of some issue with the catalog, the scan was prolonging).
Now can I run the same xcp scan with -noID syntax, so that it will not create any index file ?
Do the above finding/ask is making some meaning ? pls suggest on this.