Re: artificially break/corrupt thin pool

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



With older kernels (3.10.0.327) I had seen the error message when one tries to create lot of snapshots (100's), perform writes on those snapshots and running thin tools like thin_dump or thin_delta.

I haven't seen those with 3.10.0-514.


On 03/14/2017 08:40 AM, Thanos Makatos wrote:
>From time to time I get the error "Check of pool foo/bar failed
(status:1). Manual repair required!" and I'm writing a script that
tries to repair the thin pool and re-activate it (lvconvert --repair
foor/bar && lvchange -ay foo/bar).

However it's hard to test as I do not usually have a broken thin pool
at hand. Is there some simple way to break the thin pool and render it
"repairable"?


--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel



[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux