Accidentally Copied Lots of Small Files - Recovering from a Blown Out log and Spool. about greyhole HOT 5 OPEN

MariaDB [greyhole]> SELECT COUNT() FROM tasks;
+----------+
| COUNT() |
+----------+
| 924131 |
+----------+

78 tasks a minute = 8 days to clear?

from greyhole.

greyhole -C
All scheduled fsck tasks have now been deleted.
Specific files checks might have been queued for problematic files, and those (fsck_file) tasks will still be executed, once other tasks have been processed.

I guess these are the "Special Files Checks" since it continues.

from greyhole.

Stop the daemon, then look for and delete the fsck_file tasks queued:

(Replace MyBackups by your share name, and something/else by the folder that contained those files)

select count(*) from tasks where action = 'fsck_file' and share = 'MyBackups' and full_path LIKE 'something/else/%';
DELETE from tasks where action = 'fsck_file' and share = 'MyBackups' and full_path LIKE 'something/else/%';

You will also need to delete this folder (and all sub-folders) from the Greyhoel metadata folders, or you will get errors on each full fsck. Look in each of your storage pool drives, in the folders .gh_metastore and .gh_metastore_backup, and nuke the folders ShareName/something/else you can find there. If your shared drives are all together, you can run something like this:

ls -la /mnt/hdd*/gh/.gh_metastore*/ShareName/something/else/
# Then if you are sure it would delete the correct folders:
rm -rf /mnt/hdd*/gh/.gh_metastore*/ShareName/something/else/

Then you can restart the daemon.

Cheers.

from greyhole.

Great - lifesaver. Did all that and the service starts (allows me to start). But tailing the log and nothing is happening. Allowed me to start a FSCK and also nothing happens.

from greyhole.

Actually disregard. It's working I just had the log level set to WARN and couldn't see the BAU logs. Thank you.

from greyhole.