All of lore.kernel.org
 help / color / mirror / Atom feed
* Dumb question; please help
@ 2015-05-06 17:45 Locane
  2015-05-07  8:49 ` Zdenek Kabelac
  2015-05-07 18:04 ` Frederick Grose
  0 siblings, 2 replies; 3+ messages in thread
From: Locane @ 2015-05-06 17:45 UTC (permalink / raw)
  To: dm-devel


[-- Attachment #1.1: Type: text/plain, Size: 996 bytes --]

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.

Thanks in advance.

[-- Attachment #1.2: Type: text/html, Size: 1854 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Dumb question; please help
  2015-05-06 17:45 Dumb question; please help Locane
@ 2015-05-07  8:49 ` Zdenek Kabelac
  2015-05-07 18:04 ` Frederick Grose
  1 sibling, 0 replies; 3+ messages in thread
From: Zdenek Kabelac @ 2015-05-07  8:49 UTC (permalink / raw)
  To: dm-devel

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Dumb question; please help
  2015-05-06 17:45 Dumb question; please help Locane
  2015-05-07  8:49 ` Zdenek Kabelac
@ 2015-05-07 18:04 ` Frederick Grose
  1 sibling, 0 replies; 3+ messages in thread
From: Frederick Grose @ 2015-05-07 18:04 UTC (permalink / raw)
  To: device-mapper development


[-- Attachment #1.1: Type: text/plain, Size: 1674 bytes --]

On Wed, May 6, 2015 at 1:45 PM, Locane <locane@gmail.com> wrote:

> 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?
>

<sectors_allocated>/<total_sectors> <metadata_sectors>
​

> My LiveCD dies when the 7568 number in this example gets to the (I assume
> gibabyte) 1048576 number.  Can I increase this base size?
>

​With​

​recent dracut versions, there are startup options, rd.live.overlay.size
and rd.writable.fsimg​, that may be considered.

See
http://git.kernel.org/?p=boot/dracut/dracut.git;a=blob;f=modules.d/90dmsquash-live/dmsquash-live-root.sh;hb=HEAD

https://fedoraproject.org/wiki/LiveOS_image may also be helpful.

        --Fred


>
> I apologize again for asking such a rudimentary question on this mailing
> list, but I am desperate.
>
> Thanks in advance.
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

[-- Attachment #1.2: Type: text/html, Size: 5438 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-05-07 18:04 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-05-06 17:45 Dumb question; please help Locane
2015-05-07  8:49 ` Zdenek Kabelac
2015-05-07 18:04 ` Frederick Grose

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.