From: matthew patton <pattonme@yahoo.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] thin handling of available space
Date: Wed, 4 May 2016 14:55:33 +0000 (UTC) [thread overview]
Message-ID: <799090122.6079306.1462373733693.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: 799090122.6079306.1462373733693.JavaMail.yahoo.ref@mail.yahoo.com
On Tue, 5/3/16, Mark Mielke <mark.mielke@gmail.com> wrote:
> I get a bit lost here in the push towards BTRFS and ZFS for people with these expectations as
> I see BTRFS and ZFS as having a similar problem. They can both still fill up.
Well of course everything fills up eventually. BTRFS and ZFS are integrated systems where the FS can see into the block layer and "do" block layer activities vs the clear demarcation between XFS/EXT and LVM/MD.
If you write too much to a Thin FS today you get serious data loss. Oh sure, the metadata might have landed but the file contents sure didn't. Somebody (you?) mentioned how you seemingly were able to write 4x90GB to a 300GB block device and the FS fsck'd successfully. This doesn't happen in BTRFS/ZFS and friends. At 300.001GB you would have gotten a write error and the write operation would not have succeeded.
next parent reply other threads:[~2016-05-04 14:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <799090122.6079306.1462373733693.JavaMail.yahoo.ref@mail.yahoo.com>
2016-05-04 14:55 ` matthew patton [this message]
2016-05-03 18:19 [linux-lvm] thin handling of available space Xen
[not found] <1614984310.1700582.1462280490763.JavaMail.yahoo.ref@mail.yahoo.com>
2016-05-03 13:01 ` matthew patton
2016-05-03 15:47 ` Xen
2016-05-04 0:56 ` Mark Mielke
[not found] <1870050920.5354287.1462276845385.JavaMail.yahoo.ref@mail.yahoo.com>
2016-05-03 12:00 ` matthew patton
2016-05-03 14:38 ` Xen
2016-05-04 1:25 ` Mark Mielke
2016-05-04 18:16 ` Xen
[not found] <1684768750.3193600.1461851163510.JavaMail.yahoo.ref@mail.yahoo.com>
2016-04-28 13:46 ` matthew patton
[not found] <929635034.3140318.1461840230292.JavaMail.yahoo.ref@mail.yahoo.com>
2016-04-28 10:43 ` matthew patton
2016-04-28 18:20 ` Xen
2016-04-28 18:25 ` Xen
2016-04-29 11:23 ` Zdenek Kabelac
2016-05-02 14:32 ` Mark Mielke
2016-05-03 9:45 ` Zdenek Kabelac
2016-05-03 10:41 ` Mark Mielke
2016-05-03 11:18 ` Zdenek Kabelac
2016-05-03 10:15 ` Gionatan Danti
2016-05-03 11:42 ` Zdenek Kabelac
2016-05-03 13:15 ` Gionatan Danti
2016-05-03 15:45 ` Zdenek Kabelac
2016-05-03 12:42 ` Xen
[not found] <518072682.2617983.1461760017772.JavaMail.yahoo.ref@mail.yahoo.com>
2016-04-27 12:26 ` matthew patton
2016-04-27 21:28 ` Xen
2016-04-28 6:46 ` Marek Podmaka
2016-04-28 10:33 ` Xen
-- strict thread matches above, loose matches on Subject: below --
2016-04-23 17:53 Xen
2016-04-27 12:01 ` Xen
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=799090122.6079306.1462373733693.JavaMail.yahoo@mail.yahoo.com \
--to=pattonme@yahoo.com \
--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).