Can I thaw a bucket that has not been named properly at freeze time?

[bmw_katemcd]

We have some archived frozen buckets that are named "indexname-yyyy-mm-dd-hh-min" instead of the db_endtime_starttime_guid format. When we try to do the rebuild on these we get an error "fsck - Constraints given leave no buckets to operate on". Is this due to the odd naming of the buckets? They were archived using the ColdToFrozen.py script supplied with splunk but altered by one of our admins to write the buckets out with the new naming convention.

Is our data unthawable? Is there a command we can run to extract the correct information so we can rename the directory appropriately?

[bmw_katemcd · Accepted solution]

Answering my own question. If you open up the journal file in the bucket that's misnamed, you can extract the start and end times and use those to rename the directory to a scheme Splunk understands (db_endtime_starttime_sequence_guid). It didn't care what i used as a sequence number and the guid was grabbed from a correctly named bucket directory on one of my indexes. The process is ugly and slow but it works.