linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Middleton <scott@assuretek.com.au>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-btrfs@vger.kernel.org
Subject: Re: send/receive and bedup
Date: Wed, 14 May 2014 23:36:03 +0800	[thread overview]
Message-ID: <CAPm-YUWryMcGFop+miu+dnMBac6gf-mdJCx07XHPxdr66h3Big@mail.gmail.com> (raw)
In-Reply-To: <pan$43445$a1ed5a9d$d03f1b1$41238e2b@cox.net>

Hi



> I left this for a couple days hoping someone else with a more directly
> similar use-case would answer, but none so far, so I'll give it a go...

Thanks for getting back to me mate!


>
> First some general boilerplate.  Btrfs is still under heavy development
> and keeping current with especially the kernel is *STRONGLY* recommended,
> as every new kernel still brings lots of fixes, meaning if you're running
> an old kernel, you're running known-buggy code with fixes available in a
> current kernel.  Similarly, you probably don't want to let the btrfs-progs
> userspace tools get too outdated either, tho that's not as critical as it
> mostly means not being able to take advantage of the latest features and
> fixes for maintenance, not the risk of operational data loss if one of
> the known-fixed old-version kernel bugs hits that you have when running
> an older kernel.
>

My test environment is:
root@Ubuntu-14:~/btrfs/btrfs-progs# uname -a
Linux Ubuntu-14 3.14.1-031401-generic #201404141220 SMP Mon Apr 14
16:21:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

root@Ubuntu-14:~/btrfs/btrfs-progs# which btrfs
/usr/local/bin/btrfs
root@Ubuntu-14:~/btrfs/btrfs-progs# btrfs --version
Btrfs v3.14.1

I read so much about BtrFS that I mistaked Bedup with Duperemove.
Duperemove is actually what I am testing.

I also plan on testing SDFS - opendedup again! They have some
development since the last time I tried,  Not a fan of having to use
Java though!

> Second, as you've done some research already you're likely aware of this,
> but just in case, let me give you the link to the wiki.  If you haven't
> read up there, please do, as it's likely to be quite helpful. =:^)
>
> Memory or bookmark: https://btrfs.wiki.kernel.org


Lots of bookmarks. One of my faves is:
https://wiki.archlinux.org/index.php/Btrfs


It will be interesting on what happens. I rsync'd the clients data
from a 2TB mdadm RAID to a standard 3TB BtrFS drive, Currently running
 Duperemove on it. I reckon it will take days but it will be
interesting to see what happens.

  reply	other threads:[~2014-05-14 15:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12 12:27 send/receive and bedup Scott Middleton
2014-05-14 13:20 ` Duncan
2014-05-14 15:36   ` Scott Middleton [this message]
2014-05-19  1:07     ` Marc MERLIN
2014-05-19 13:00       ` Scott Middleton
2014-05-19 16:01         ` Brendan Hide
2014-05-19 17:12           ` Konstantinos Skarlatos
2014-05-19 17:55             ` Mark Fasheh
2014-05-19 17:59             ` Austin S Hemmelgarn
2014-05-19 18:27               ` Mark Fasheh
2014-05-19 17:38           ` Mark Fasheh
2014-05-19 22:07             ` Konstantinos Skarlatos
2014-05-20 11:12               ` Scott Middleton
2014-05-20 22:37               ` Mark Fasheh
2014-05-20 22:56                 ` Konstantinos Skarlatos
2014-05-21  0:58                   ` Chris Murphy
2014-05-23 15:48                     ` Konstantinos Skarlatos
2014-05-23 16:24                       ` Chris Murphy
2014-05-21  3:59           ` historical backups with hardlinks vs cp --reflink vs snapshots Marc MERLIN
2014-05-22  4:24             ` Russell Coker

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=CAPm-YUWryMcGFop+miu+dnMBac6gf-mdJCx07XHPxdr66h3Big@mail.gmail.com \
    --to=scott@assuretek.com.au \
    --cc=linux-btrfs@vger.kernel.org \
    /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).