On Mon, Nov 11, 2013 at 04:32:33PM -0500, Mike Snitzer wrote:
> On Mon, Nov 11 2013 at 4:19pm -0500,
> Alasdair G Kergon <agk@xxxxxxxxxx> wrote:
> > > + DMERR("unable to shrink cache due to dirty blocks");
> > This error is highly undesirable: part of a device has been removed
> > while it is still needed!
> Huh? The device still had dirty blocks, so the cache wasn't resized.
The device no longer has those dirty blocks: you already removed them
(otherwise you wouldn't have reached this point).
> Use the cleaner policy to purge the cache first.
But how do you do that without also cleaning the part of the cache that
you're keeping? (For example, why should it be necessary to stop using
your preferred cache policy for a while and clean the entire cache just in
order to reduce the size of the cache slightly?)
If the current situation is temporary then can we indicate what a better
solution is likely to look like and whether it is likely still to use this
proposed shrinker interface or whether it could replace it with something else?
Alasdair
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
