> I have a file system that I have tried to scan multiple times and it alway > gets stuck after what I believe is when it is at the very end of the process. > I thought for a long time that it was a problem with my lustre file system > (fsck) but recently that was performed and the scans still will hang.
Was this run with the --no-gc flag? (ie, is it still working on the filesystem side of things, or doing database shuffling) I've found on our system (you may have seen this in the archives) that 'lsof' helps to point out which directory the scan is currently in - ours appears to lock up when we have users with huge directories. it's still running, but no visible indication. if you have access to the database server, 'show processlist' (or show full processlist' may help too - you can see which threads are sleeping vs running any sort of queries. > I have been looking through the archives at any post having to do with > stalled scan and came across the gstack command that I had not heard of > before. oh - neither had I - I'll have a look on our system next time it scans Hope some of these help Andrew ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ robinhood-support mailing list robinhood-support@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/robinhood-support
