From: David Howells <dhowells@redhat.com>
To: Andreas Dilger <adilger@dilger.ca>
Cc: dhowells@redhat.com, Christoph Hellwig <hch@lst.de>,
Qu Wenruo <quwenruo.btrfs@gmx.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
linux-ext4 <linux-ext4@vger.kernel.org>,
linux-xfs <linux-xfs@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Problems with determining data presence by examining extents?
Date: Wed, 15 Jan 2020 23:09:03 +0000 [thread overview]
Message-ID: <7026.1579129743@warthog.procyon.org.uk> (raw)
In-Reply-To: <7233E240-8EE5-4CD1-B8A4-A90925F51A1B@dilger.ca>
Andreas Dilger <adilger@dilger.ca> wrote:
> > It would also have to say that blocks of zeros shouldn't be optimised away.
>
> I don't necessarily see that as a requirement, so long as the filesystem
> stores a "block" at that offset, but it could dedupe all zero-filled blocks
> to the same "zero block". That still allows saving storage space, while
> keeping the semantics of "this block was written into the file" rather than
> "there is a hole at this offset".
Yeah, that's more what I was thinking of. Provided I can find out that
something is present, it should be fine.
David
next prev parent reply other threads:[~2020-01-15 23:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 16:48 Problems with determining data presence by examining extents? David Howells
2020-01-14 22:49 ` Theodore Y. Ts'o
2020-01-15 3:54 ` Qu Wenruo
2020-01-15 12:46 ` Andreas Dilger
2020-01-15 13:10 ` Qu Wenruo
2020-01-15 13:31 ` Christoph Hellwig
2020-01-15 19:48 ` Andreas Dilger
2020-01-16 10:16 ` Christoph Hellwig
2020-01-15 20:55 ` David Howells
2020-01-15 22:11 ` Andreas Dilger
2020-01-15 23:09 ` David Howells [this message]
2020-01-26 18:19 ` Zygo Blaxell
2020-01-15 14:35 ` David Howells
2020-01-15 14:48 ` Christoph Hellwig
2020-01-15 14:59 ` David Howells
2020-01-16 10:13 ` Christoph Hellwig
2020-01-17 16:43 ` David Howells
2020-01-15 14:20 ` David Howells
2020-01-15 8:38 ` Christoph Hellwig
2020-01-15 13:50 ` David Howells
2020-01-15 14:05 ` David Howells
2020-01-15 14:24 ` Qu Wenruo
2020-01-15 14:50 ` David Howells
2020-01-15 14:15 ` David Howells
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=7026.1579129743@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=adilger@dilger.ca \
--cc=clm@fb.com \
--cc=darrick.wong@oracle.com \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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).