From: Xen <list@xenhideout.nl>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Lvm think provisioning query
Date: Tue, 03 May 2016 17:51:34 +0200 [thread overview]
Message-ID: <f56c5af2e35182a73de542adb66e3af5@dds.nl> (raw)
In-Reply-To: <5728BA8A.3040009@redhat.com>
Zdenek Kabelac schreef op 03-05-2016 16:49:
> Expecting you run out-of-space in thin-pool and nothing bad can
> happens is naive ATM - we are cooperating at least with XFS/ext4
> developers to solve some corner case, but there is still a lot of work
> to do as we exercise quite unusual error paths for them.
You also talked about seeing if you could have these filesystems work
more in alignment with block (extent) boundaries, right?
I mean something that agrees more with allocation requests, so to speak.
next prev parent reply other threads:[~2016-05-03 15:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 12:33 [linux-lvm] Lvm think provisioning query Bhasker C V
2016-04-27 14:33 ` Zdenek Kabelac
2016-04-28 14:36 ` Bhasker C V
2016-04-29 8:13 ` Zdenek Kabelac
2016-05-03 6:59 ` Bhasker C V
2016-05-03 9:54 ` Zdenek Kabelac
2016-05-03 12:21 ` Bhasker C V
2016-05-03 14:49 ` Zdenek Kabelac
2016-05-03 15:51 ` Xen [this message]
2016-05-03 16:27 ` Zdenek Kabelac
2016-05-03 17:07 ` Gionatan Danti
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=f56c5af2e35182a73de542adb66e3af5@dds.nl \
--to=list@xenhideout.nl \
--cc=linux-lvm@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;
as well as URLs for NNTP newsgroup(s).