On Thu, Aug 29 2013 at 10:37am -0400, Mikulas Patocka <mpatocka@xxxxxxxxxx> wrote: > As I said - I think it would be better to remove the immutable flag than > to create more flags to bypass it. Immutable was introduced to prevent dangerous scenarios that weren't accounted for in original design, etc. It solved your crash when you rep;aced a thin-pool with an empty table. immutable is staying for now. And as it turns out allowing error target to override an immutable target was always held to be a logical/possible future relaxation of the immutable constraint. Mike -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
