Yeah, I think it make sense for shutdown_bcache to adjust. Currently it does this:
# bcache device removal should be fast but in an extreme
# case, might require the cache device to flush large
# amounts of data to a backing device. The strategy here
# is to wait for approximately 30 seconds but to check
# frequently since curtin cannot proceed until devices
# cleared.
removal_retries = [0.2] * 150 # 30 seconds total
1200 seems extreme to me. Did you try anything lower than that?
I'd be more inclined to try 5 minutes...
remove_retries = [0.2] * 1500 # 300 seconds/5 min total
Yeah, I think it make sense for shutdown_bcache to adjust. Currently it does this:
# bcache device removal should be fast but in an extreme
# case, might require the cache device to flush large
# amounts of data to a backing device. The strategy here
# is to wait for approximately 30 seconds but to check
# frequently since curtin cannot proceed until devices
# cleared.
removal_retries = [0.2] * 150 # 30 seconds total
1200 seems extreme to me. Did you try anything lower than that?
I'd be more inclined to try 5 minutes...
remove_retries = [0.2] * 1500 # 300 seconds/5 min total
Or we could scale it up like:
remove_retries = ([0.2] * 150 + [20] * 15) # 30 seconds + 5 minutes