From: Les Mikesell <lesmikesell@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Data deduplication in LVM?
Date: Wed, 10 Jun 2009 13:54:21 -0500 [thread overview]
Message-ID: <4A30015D.1010409@gmail.com> (raw)
In-Reply-To: <4855BFEA-C772-4B98-A18E-C406FD5737DD@karlsbakk.net>
Roy Sigurd Karlsbakk wrote:
> Hi all
>
> I've been reading up a little about data deduplication, and have been in
> search for an OSS filesystem with dedup without much luck. While testing
> snapshots and so on in LVM, I started wondering if dedup would be better
> off in LVM than in the filesystem. Would it be possible/efficient to add
> dedup to the LVM layer, or perhaps a layer above LVM? This could make
> dedup work for all or most of filesystems. Make a hash table with 4k (or
> whatever) blocks, make virtual blocks pointing to the physical blocks
> and run a remapping/deduping job at night. If written to, copy-on-write
> could be used to increase speed.
>
> Is this nonsense, or might it be an idea?
This is "supposed" to be coming in the next OpenSolaris/ZFS release (per
the roadmap with the just-released 2009.06 version).
--
Les Mikesell
lesmikesell@gmail.com
next prev parent reply other threads:[~2009-06-10 18:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 18:41 [linux-lvm] Data deduplication in LVM? Roy Sigurd Karlsbakk
2009-06-10 18:48 ` Ray Van Dolson
2009-06-10 18:54 ` Les Mikesell [this message]
2009-06-10 18:59 ` Roy Sigurd Karlsbakk
2009-06-10 19:30 ` Les Mikesell
2009-06-10 19:33 ` Brian J. Murrell
2009-06-10 19:34 ` Ray Van Dolson
2009-06-10 19:04 ` Roy Sigurd Karlsbakk
2009-06-10 22:30 ` Stuart D. Gathman
2009-06-11 10:19 ` Roy Sigurd Karlsbakk
2009-06-11 12:30 ` Les Mikesell
2009-06-11 15:35 ` Les Mikesell
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=4A30015D.1010409@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 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.