From: Hubert Kario <hka@qbs.com.pl>
To: "Martin Křížek" <martin.krizek@gmail.com>
Cc: linux-btrfs@vger.kernel.org, lczerner@redhat.com
Subject: Re: Online Deduplication for Btrfs (Master's thesis)
Date: Mon, 17 Dec 2012 14:12:38 +0100 [thread overview]
Message-ID: <5848153.J4MMzXfUGd@bursa22> (raw)
In-Reply-To: <CAMiUzp95BXF8fcNb9EQQsrz1NpDtX9qr=FdC9C=+r3KYkYxgzw@mail.gmail.com>
On Monday 17 of December 2012 13:05:01 Martin Křížek wrote:
> * Limitations
> Not really limitations, but this is a list of situations when dedup will
> not be triggered:
> - compression - basically, dedup is kind of compression, might be worth to
> into it in the future though
I don't see why it would be incompatible, compressed blocks are data like
any other. COW and subvolume snapshots work with compressed nodes just as
well as with regular ones...
> - data across subvolumes
Wasn't the "cp --reflink" across subvolumes merged to mainline quite a bit
ago? Under 3.6.9 it works fine for me... Also, the blocks are shared between
subvolumes if the other subvolume is a snapshot of the first one.
Besides, I think that doing a rsync from remote server and snapshotting the
subvolume dedicated for server will be the standard approach.
Regards,
--
Hubert Kario
QBS - Quality Business Software
02-656 Warszawa, ul. Ksawerów 30/85
tel. +48 (22) 646-61-51, 646-74-24
www.qbs.com.pl
next prev parent reply other threads:[~2012-12-17 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 12:05 Online Deduplication for Btrfs (Master's thesis) Martin Křížek
2012-12-17 13:12 ` Hubert Kario [this message]
2012-12-19 16:58 ` Martin Křížek
2012-12-17 13:33 ` Alexander Block
2012-12-18 1:31 ` Chris Mason
2013-01-07 17:27 ` Martin Křížek
2013-03-17 22:57 ` Martin Křížek
2012-12-19 17:40 ` Martin Křížek
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=5848153.J4MMzXfUGd@bursa22 \
--to=hka@qbs.com.pl \
--cc=lczerner@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin.krizek@gmail.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.