All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Clark <anthony@merit.edu>
To: linux-lvm@redhat.com
Subject: [linux-lvm] deduplication, at LVM level or FS level?
Date: Mon, 16 Nov 2009 17:09:32 -0500 (EST)	[thread overview]
Message-ID: <951302003.8081441258409372728.JavaMail.root@crono> (raw)
In-Reply-To: <2112453070.8081291258409320087.JavaMail.root@crono>

Hi All,

I'm dealing with ever-larger HSM and backups, as I'm sure many of us are.  I was wondering where the "best" place to perform data deduplication was? (compression, ha!)

Should dedup happen at the filesystem level or the LVM level?  I'm somewhat motivated to try to shoehorn lessfs' code into something that doesn't require FUSE, but I'm still at the early stages of examining this.

Anyone doing anything similar?

Thanks

Anthony

       reply	other threads:[~2009-11-16 22:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2112453070.8081291258409320087.JavaMail.root@crono>
2009-11-16 22:09 ` Anthony Clark [this message]
2009-11-17 22:38   ` [linux-lvm] deduplication, at LVM level or FS level? Christian Kujau

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=951302003.8081441258409372728.JavaMail.root@crono \
    --to=anthony@merit.edu \
    --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.