All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maciej Marcin Piechotka <uzytkownik2@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Rename BTRfs to MuchSlowerFS ?
Date: Fri, 16 Sep 2011 08:21:24 +0200	[thread overview]
Message-ID: <1316154091.28427.3.camel@picard> (raw)
In-Reply-To: <CAG1y0sdv=GwgRAd1suTGhzVB=A1dUsZ=fjiE67QsuGQCCQwSjw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]

On Fri, 2011-09-16 at 05:16 +0700, Fajar A. Nugraha wrote:
> On Fri, Sep 16, 2011 at 2:37 AM, Felix Blanke <felixblanke@gmail.com> wrote:
> > I'm using btrfs since one year now and it's quite fast. I don't feel any
> > differences to other filesystems. Never tried a benchmark but for my daily
> > work it's nice.
> 
> Your workload must be light :)
> 

I recently repeatedly rsync whole partitions (>30GB) without ill
effects. (ok - first sync took whole 1s).

> >
> > The advantage to ext4 for me is the build in raid1 and the snapshots. I'm
> > using the snapshot feature for my local backups. I like it because it's
> > really easy and uses very few storage. A simple "Snapshot -> Rsync to a
> > different disk -> Snapshot" script is the perfect local backup method.
> >
> 
> you've never used zfs have you :)
> 
> For that purpose, think "same feature as btrfs snapshot + rsync" but
> without needing rsync. This can be very useful as the process of rsync
> determining what data to transfer can be quite CPU/disk intensive.

Now I'm curious - how do zsf get data off the partition without rsync?

Regards

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-09-16  6:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-05 13:51 Rename BTRfs to MuchSlowerFS ? Swâmi Petaramesh
2011-09-05 14:00 ` Hugo Mills
2011-09-05 14:20   ` Roman Mamedov
2011-09-05 17:10     ` Elric Milon
2011-09-05 14:17 ` David McBride
2011-09-05 19:25 ` Sergei Trofimovich
2011-09-06 15:30   ` Swâmi Petaramesh
2011-09-06 17:11     ` Fajar A. Nugraha
2011-09-07 14:15       ` Swâmi Petaramesh
2011-09-15 19:37         ` Felix Blanke
2011-09-15 22:16           ` Fajar A. Nugraha
2011-09-16  6:21             ` Maciej Marcin Piechotka [this message]
2011-09-16  6:42               ` Fajar A. Nugraha
2011-09-16  8:39                 ` Maciej Marcin Piechotka
  -- strict thread matches above, loose matches on Subject: below --
2011-09-05 16:23 Tomasz Chmielewski
2011-09-05 16:25 ` Christoph Hellwig
2011-09-05 16:29   ` Hugo Mills
2011-09-08  7:04     ` youagree

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=1316154091.28427.3.camel@picard \
    --to=uzytkownik2@gmail.com \
    --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 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.