From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: Zdenek Kabelac <zdenek.kabelac@gmail.com>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] thin: 235:2 pool target (735616 blocks) too small: expected 809216
Date: Thu, 02 Jun 2016 15:27:18 -0400 [thread overview]
Message-ID: <1464895638.13773.54.camel@interlinx.bc.ca> (raw)
In-Reply-To: <6504f4cb-8f17-390a-ec9f-0cc6826b23ec@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 750 bytes --]
On Thu, 2016-06-02 at 14:15 +0200, Zdenek Kabelac wrote:
> Yep that might explain 'missing' surrouding details...
> Basically any write might result in thin-pool running out of
> threshold
> and requireing new space
Ahhh. I was wondering if the resize in question could be some kind of
implicit resizing done by the "hidden" thin-pool maintenance. I'm
fairly sure he knows zilch about LVM and resizing. :-)
> - what's unclear is the later failure which
> would be really good to know....
Is there anything in particular I can look for in the logs that would
indicate when this implicit resizing was happening to look for other
activity that might have caused a problem?
> Ops - so once again ;)
Cheers. :-)
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-06-02 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 10:57 [linux-lvm] thin: 235:2 pool target (735616 blocks) too small: expected 809216 Brian J. Murrell
2016-05-31 11:22 ` Zdenek Kabelac
2016-06-01 22:52 ` Brian J. Murrell
2016-06-02 9:11 ` Zdenek Kabelac
2016-06-02 10:49 ` Brian J. Murrell
2016-06-02 12:15 ` Zdenek Kabelac
2016-06-02 19:27 ` Brian J. Murrell [this message]
2016-06-02 19:32 ` Zdenek Kabelac
2016-06-02 21:18 ` Brian J. Murrell
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=1464895638.13773.54.camel@interlinx.bc.ca \
--to=brian@interlinx.bc.ca \
--cc=linux-lvm@redhat.com \
--cc=zdenek.kabelac@gmail.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.