On 12/08/2016 04:23 AM, Zdenek Kabelac wrote:
I'm sorry but you've attached so little information there is no way to give you some useful hint.
Actually you did. :-) I was just asking what tool(s) I should be using to "check/repair" the metadata. (Google is oddly silent on the subject.) Your reference to "cache_check" was the hint I needed to get started. Running cache_repair against the metadata device gives me this error: transaction_manager::new_block() couldn't allocate new block I strongly suspect that my metadata device is too small. It was sized with the algorithm that I posted to this list about a year ago: https://www.redhat.com/archives/dm-devel/2015-November/msg00221.html Looking at the source code for cache_metadata_size, I see that it adds additional space for "hints", which the old algorithm didn't account for. Assuming that my suspicion is correct, is there any straightforward way to recover this cache device? I do need to reclaim the storage used by the origin device, so I'm guessing that my best course of action will be to simply recreate the cache device with a sufficiently large metadata device. Thanks! -- ======================================================================== Ian Pilcher arequipeno@xxxxxxxxx -------- "I grew up before Mark Zuckerberg invented friendship" -------- ======================================================================== -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
