All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Vladimir Smolensky <arizal@gmail.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: dm-cache fs corruption
Date: Mon, 2 Dec 2013 09:47:57 -0500	[thread overview]
Message-ID: <20131202144756.GB5331@redhat.com> (raw)
In-Reply-To: <CALwk7=yrb4awYXdyGdf5fAY8pW3=k6b+eabeDA2mooeyetBWYg@mail.gmail.com>

On Sat, Nov 30 2013 at  9:28am -0500,
Vladimir Smolensky <arizal@gmail.com> wrote:

> Hello, the device broke after about a day:
> 
> dmesg:
> 
> [83086.878182] device-mapper: space map metadata: unable to allocate new
> metadata block
> [83088.879861] device-mapper: space map metadata: unable to allocate new
> metadata block
> [83089.414700] device-mapper: space map metadata: unable to allocate new
> metadata block
> [83089.414706] device-mapper: cache: could not commit metadata for accurate
> status
> [83090.881533] device-mapper: space map metadata: unable to allocate new
> metadata block
> [83092.883142] device-mapper: space map metadata: unable to allocate new
> metadata block
> [83094.884719] device-mapper: space map metadata: unable to allocate new
> metadata block
> [83096.886355] device-mapper: space map metadata: unable to allocate new
> metadata block
> [83097.712195] device-mapper: space map metadata: unable to allocate new
> metadata block
> [83097.712200] device-mapper: cache: could not commit metadata for accurate
> status
> [83098.283947] device-mapper: space map metadata: unable to allocate new
> metadata block
> [83098.283952] device-mapper: cache: could not commit metadata for accurate
> status
> [83098.729396] device-mapper: space map metadata: unable to allocate new
> metadata block
> [83098.729401] device-mapper: cache: could not commit metadata for accurate
> status
> 
> dmsetup status:
> storage: 0 40963653632 cache 249856/249856 26968230 2678513 711227 30042060
> 0 248746 248729 0 1 writeback 2 migration_threshold 100000000 4
> random_threshold 4 sequential_threshold 10000000
> 
> Obviously the metadata partition is full but accourding to the formula I
> use it should be more than enough =>  4 MB + ( 16 bytes * nr_blocks ) I get
> 13341184 ~ 13MB and metadata partiton is 1024MB
>
> device sizes:
>  # blockdev --report
> RO    RA   SSZ   BSZ   StartSec            Size   Device
> rw   256   512  4096          0     26843414528   /dev/sda
> rw   256   512  4096       2048      4094689280   /dev/sda1
> rw   256   512  4096    7999488     22746759168   /dev/sda2
> rw  2048   512  4096          0  20973392756736   /dev/sdb
> rw  2048   512  4096       2048  20973390659584   /dev/sdb1
> rw  2048   512  4096          0   2397799710720   /dev/sdc
> rw  2048   512  4096       2048      1023410176   /dev/sdc1
> rw  2048   512  4096    2000896   2396774203392   /dev/sdc2
> rw  2048   512   512          0  20973390659584   /dev/dm-0
>
> What am I doing wrong?

Not clear yet.  Something is causing you to run out of metadata blocks.

Please provide the output of 'dmsetup table'.  Last time you did the
metadata device that was provided to the cache target was _not_ 1024MB.

Mike

  reply	other threads:[~2013-12-02 14:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 10:24 dm-cache fs corruption Vladimir Smolensky
2013-11-13 13:10 ` Joe Thornber
2013-11-13 13:48   ` Vladimir Smolensky
2013-11-13 14:31     ` Mike Snitzer
2013-11-13 14:41     ` Joe Thornber
2013-11-13 15:19       ` Vladimir Smolensky
2013-11-13 16:29         ` Vladimir Smolensky
2013-11-13 18:39           ` Mears, Morgan
2013-11-14 14:38             ` Joe Thornber
2013-11-14 15:21               ` Vladimir Smolensky
2013-11-14 20:22                 ` Vladimir Smolensky
2013-11-15 13:01                   ` Vladimir Smolensky
2013-11-28 16:50                     ` Vladimir Smolensky
2013-11-28 17:28                       ` Joe Thornber
2013-11-29 13:34                         ` Vladimir Smolensky
2013-11-29 15:06                           ` Vladimir Smolensky
2013-11-30 14:28                             ` Vladimir Smolensky
2013-12-02 14:47                               ` Mike Snitzer [this message]
2013-11-13 19:32           ` Mike Snitzer
2014-01-22  1:04 ` Vladimir Smolensky

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=20131202144756.GB5331@redhat.com \
    --to=snitzer@redhat.com \
    --cc=arizal@gmail.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.