All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: dm-devel@redhat.com
Subject: Re: [PATCH 1/6] dm cache: cache shrinking support
Date: Mon, 11 Nov 2013 16:32:33 -0500	[thread overview]
Message-ID: <20131111213232.GA5099@redhat.com> (raw)
In-Reply-To: <20131111211934.GB24324@agk-dp.fab.redhat.com>

On Mon, Nov 11 2013 at  4:19pm -0500,
Alasdair G Kergon <agk@redhat.com> wrote:

> On Mon, Nov 11, 2013 at 12:20:43PM -0500, Mike Snitzer wrote:
> > From: Joe Thornber <ejt@redhat.com>
> > 
> > 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.

  reply	other threads:[~2013-11-11 21:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-11 17:20 [PATCH for-3.13 0/6] dm cache: simple cache block invalidation interface Mike Snitzer
2013-11-11 17:20 ` [PATCH 1/6] dm cache: cache shrinking support Mike Snitzer
2013-11-11 21:19   ` Alasdair G Kergon
2013-11-11 21:32     ` Mike Snitzer [this message]
2013-11-11 21:48       ` Alasdair G Kergon
2013-11-11 21:50       ` Mike Snitzer
2013-11-11 22:09         ` Alasdair G Kergon
2013-11-11 22:15           ` Alasdair G Kergon
2013-11-11 23:06             ` Mike Snitzer
2013-11-11 23:17               ` Alasdair G Kergon
2013-11-11 23:34                 ` Mike Snitzer
2013-11-11 23:03       ` Alasdair G Kergon
2013-11-11 23:08         ` Mike Snitzer
2013-11-11 17:20 ` [PATCH 2/6] dm cache: add passthrough mode Mike Snitzer
2013-11-11 23:40   ` Alasdair G Kergon
2013-11-11 17:20 ` [PATCH 3/6] dm cache metadata: check the metadata version when reading the superblock Mike Snitzer
2013-11-11 17:20 ` [PATCH 4/6] dm cache policy mq: reduce memory requirements Mike Snitzer
2013-11-11 17:20 ` [PATCH 5/6] dm cache: add remove_cblock method to policy interface Mike Snitzer
2013-11-12  0:18   ` Alasdair G Kergon
2013-11-11 17:20 ` [PATCH 6/6] dm cache: add cache block invalidation support Mike Snitzer
2013-11-12  0:46   ` Alasdair G Kergon
2013-11-12 17:35     ` Mike Snitzer
2013-11-12 19:26       ` Mike Snitzer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131111213232.GA5099@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.