From: Les Mikesell <lesmikesell@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Data deduplication for Linux : lessfs
Date: Wed, 24 Jun 2009 15:59:37 -0500 [thread overview]
Message-ID: <4A4293B9.4090200@gmail.com> (raw)
In-Reply-To: <02E64FEE-285B-4C41-93FE-9DC40E1A4538@karlsbakk.net>
Roy Sigurd Karlsbakk wrote:
> >>>> I am thinking about starting to work on a data deduplicating
>>>> blockdevice, a kernel module called blockless.
>>> If done smartly, this may perhaps be possible, but the problem is the
>>> filesystem's metadata. Is this going to be dedup'ed? How much will
>>> this take? A simple backup will update atime on all the files backed
>>> up, and although atime isn't always wanted or needed, the problem
>>> occurs elsewhere.
>>
>> Block level deduplication isn't going to know/care about the
>> difference between file contents and metadata. It is either stored in
>> blocks that match other blocks or not and the difference should not be
>> visible to the filesystem living on top of the block device.
>
>
> My point exactly. If dedup was to be done on the block layer, you'd need
> flag to say "do not dedup this".
Why? How can it possibly make any difference? It's not likely that
you'd have dupes in the metadata block, but if you do it doesn't matter
that they are transparently mapped into one. You need a copy-on-write
mechanism anyway since if you write to either they won't be dups any more.
--
Les Mikesell
lesmikesell@gmail.com
next prev parent reply other threads:[~2009-06-24 20:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 15:12 [linux-lvm] Data deduplication for Linux : lessfs Mark Ruijter
2009-06-24 18:50 ` Roy Sigurd Karlsbakk
2009-06-24 19:25 ` Mark Ruijter
2009-06-24 19:43 ` Roy Sigurd Karlsbakk
2009-06-24 19:32 ` Greg Freemyer
2009-06-24 20:04 ` Les Mikesell
2009-06-24 20:09 ` Roy Sigurd Karlsbakk
2009-06-24 20:59 ` Les Mikesell [this message]
2009-06-24 21:03 ` malahal
2009-06-24 21:21 ` Les Mikesell
2009-06-24 20:12 ` Mark Ruijter
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=4A4293B9.4090200@gmail.com \
--to=lesmikesell@gmail.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).