From: Heinz Mauelshagen <heinzm@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: How does dm-thinp handle the our of space error?
Date: Wed, 09 Mar 2011 09:56:19 +0100 [thread overview]
Message-ID: <1299660979.3310.5.camel@o> (raw)
In-Reply-To: <AANLkTi=HYPv+U-JiBbjrhAHrZOXVihs2LaGniA_m=r5O@mail.gmail.com>
On Wed, 2011-03-09 at 11:59 +0800, Xie Gang wrote:
> Hi,
>
> The storage may run out of space and could not provision the space.
> So, how does thinp handle such error since thinp is transparent to
> uper layer filesystem?
It either postpones the bios until userspace has reacted growing the
pool _or_ it errors the ios depending on the related policy set.
This is defined by constructore parameter
* 4: policy = "error|postpone":
* if pool runs full, bios will be errored or postponed
* (ie. application writes will stall)
Heinz
>
> Thanks,
>
> --
> Xie Gang
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2011-03-09 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 3:59 How does dm-thinp handle the our of space error? Xie Gang
2011-03-09 8:56 ` Heinz Mauelshagen [this message]
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=1299660979.3310.5.camel@o \
--to=heinzm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox