On Mon, Nov 11 2013 at 4:19pm -0500,
Alasdair G Kergon <agk@xxxxxxxxxx> wrote:
> On Mon, Nov 11, 2013 at 12:20:43PM -0500, Mike Snitzer wrote:
> > From: Joe Thornber <ejt@xxxxxxxxxx>
> >
> > Allow a cache to shrink if the blocks being removed from the cache are
> > not dirty.
>
> Please would you document the intended procedure here?
I'm not rebasing this patch (and in turn all commits that follow) to
tweak this header. We can add information to cache.txt as a follow-on
commit.
> > + 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.
> How does someone go about reducing the size of the cache avoiding this
> error? (Analogy: to reduce size of a filesystem you run a filesystem
> resize process before reducing the size of the block device.)
Use the cleaner policy to purge the cache first.
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
