All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <Anand.Jain@oracle.com>
To: Casper Bang <casper.bang@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Experiences: Why BTRFS had to yield for ZFS
Date: Tue, 18 Sep 2012 13:28:44 +0800	[thread overview]
Message-ID: <5058068C.4040704@oracle.com> (raw)
In-Reply-To: <CALdWcbiW2ctG50ZCSzpTHA8t1CAhwTj66=GCoLcAFjGsjFBQJw@mail.gmail.com>



> A script on the test server, would then apply Oracle archive files
> from the production environment to this Oracle sync database, every
> 10'th minute, effectively making it near up-to-date with production.

> The most reliable way to do this was with a simple NFS mount (rather
> than rsync or samba). The idea then was, that it would be very fast
> and easy to make a new snapshot of the sync database, start it up, and
> voila you'd have a new instance ready to play with. A desktop machine


  archive-log-apply script - if you could, can you share the
  script itself ? or provide more details about the script.
  (It will help to understand the work-load in question).

Thanks, Anand

  parent reply	other threads:[~2012-09-18  5:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-17  8:45 Experiences: Why BTRFS had to yield for ZFS Casper Bang
2012-09-17  9:15 ` Ralf Hildebrandt
2012-09-17  9:55   ` Casper Bnag
2012-09-17 10:05     ` Avi Miller
2012-09-17 10:47       ` Casper Bnag
2012-09-17 10:58         ` Avi Miller
2012-09-18 16:48       ` Andrew McGlashan
2012-09-18 21:46         ` Avi Miller
2012-09-18  5:28 ` Anand Jain [this message]
2012-09-19  7:28   ` Casper Bang
2012-09-19  7:36     ` Fajar A. Nugraha
2012-09-19  8:09       ` Casper Bang
2012-09-18 23:08 ` Gregory Farnum
2012-09-19 15:25 ` Chris Mason
2012-09-19 19:43   ` Casper Bang
2012-10-08 14:38   ` Casper Bang
2012-10-08 20:59     ` Avi Miller

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=5058068C.4040704@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=casper.bang@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.