All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: Greg Stark <stark@mit.edu>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: How to force a snapshot status to valid when I know	very well it's valid?
Date: Fri, 21 Dec 2012 23:13:11 +0000	[thread overview]
Message-ID: <20121221231311.GD14851@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <CAM-w4HPxTMGQd76C_Dqt56vQ1WFA7KrG4o3fbQWU1x5y=XHm5Q@mail.gmail.com>

On Fri, Dec 21, 2012 at 10:54:21PM +0000, Greg Stark wrote:
> took about 30 minutes. I don't know why or what happened there. But it

Big snapshots take a long time to load - the whole cow area has to be
scanned to generate the list of blocks represented on it.

(Large thin snapshots don't have this shortcoming.)

Alasdair

  reply	other threads:[~2012-12-21 23:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-21 18:31 How to force a snapshot status to valid when I know very well it's valid? Greg Stark
2012-12-21 18:46 ` Frederick Grose
2012-12-21 22:54   ` Greg Stark
2012-12-21 23:13     ` Alasdair G Kergon [this message]
2012-12-21 23:35       ` Greg Stark
2013-01-02 17:23         ` Alasdair G Kergon

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=20121221231311.GD14851@agk-dp.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=stark@mit.edu \
    /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.