All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: dm-devel@redhat.com
Subject: Re: Dumb question; please help
Date: Thu, 07 May 2015 10:49:33 +0200	[thread overview]
Message-ID: <554B271D.2080006@redhat.com> (raw)
In-Reply-To: <CAC5dixFNZ_FBQ8osQiCgDuvXrWBNydC2A173o4RfYqcWCX814Q@mail.gmail.com>

Dne 6.5.2015 v 19:45 Locane napsal(a):
> Hello, I apologize in advance for asking this question, but I can't seem to
> find the information in documentation or anything online.
>
> Short explanation:
>
> - I have a CentOS 6.6 LiveCD that is dying after lots of file system thrash
> - I use "dmsetup status" to check on when it's dying
> - I don't know what the numbers in "dmsetup status" represent - they're not
> labeled
>
> Can anyone answer this question
> <http://superuser.com/questions/900783/dmsetup-status-fields-explained> or
> label the following fields for me and explain what they are?
>
> [root@localhost ~]# dmsetup status
> live-osimg-min: 0 4194304 snapshot 1272/1272 16
> live-rw: 0 4194304 snapshot 7568/1048576 40
>
> What are the <number>/<number>s?  What is the 2 digit number following them?
>
> My LiveCD dies when the 7568 number in this example gets to the (I assume
> gibabyte) 1048576 number.  Can I increase this base size?
>
> I apologize again for asking such a rudimentary question on this mailing list,
> but I am desperate.
>


I'd say your snapshot volume 'live-osimg-min' has got out of space - and as 
such it has been already invalidated (data are LOST).

The snapshot has 'reserved' space for  COW blocks - when this space is 
exhausted, snapshot is lost as it cannot hold any more exception blocks.

Normally you could run 'dmeventd' and monitor 'free' space in snapshot and let 
the tool to resize snapshot to add more space, but in your case it's already 
too late.

Also I'd recommend to learn how to use 'lvm2' commands  before you start to 
play with low level dmsetup commands.

And to satisfy your curiosity about what those numbers means - here is the 
full description:
https://www.kernel.org/doc/Documentation/device-mapper/snapshot.txt

Regards

Zdenek

  reply	other threads:[~2015-05-07  8:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 17:45 Dumb question; please help Locane
2015-05-07  8:49 ` Zdenek Kabelac [this message]
2015-05-07 18:04 ` Frederick Grose

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=554B271D.2080006@redhat.com \
    --to=zkabelac@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.