Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: "Ask Bjørn Hansen" <ask@develooper.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs "stuck" on
Date: Sat, 23 Mar 2013 00:12:01 +0600	[thread overview]
Message-ID: <20130323001201.2bbbb817@natsu> (raw)
In-Reply-To: <36071CA2-8A29-4526-8523-7EB40F1C86A6@develooper.com>

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

On Thu, 21 Mar 2013 11:56:37 -0700
Ask Bjørn Hansen <ask@develooper.com> wrote:

> Hello,
> 
> A few weeks ago I replaced a ZFS backup system with one backed by btrfs. A script loops over a bunch of hosts rsyncing them to each their own subvolume.  After each rsync I snapshot the "host-specific" subvolume.
> 
> The "disk" is an iscsi disk that in my benchmarks performs roughly like a local raid with 2-3 SATA disks.

I think you should re-verify if this is still the case. Maybe your block
device performance suddenly plummeted for some other unrelated issue?

The simplest test would be "hdparm -t /dev/sdc".

Personally I use btrfs on top of an MD raid accessed over network via NBD (and
AoE before), without any major issues. Though my workload is perhaps somewhat
lighter than what you describe.

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2013-03-22 18:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 18:56 btrfs "stuck" on Ask Bjørn Hansen
2013-03-22 17:37 ` Mitch Harder
2013-03-24  8:09   ` Ask Bjørn Hansen
2013-03-22 18:12 ` Roman Mamedov [this message]
2013-03-24  8:07   ` Ask Bjørn Hansen
2013-03-29 17:12 ` David Sterba
2013-04-02 15:45   ` Alex Lyakas
  -- strict thread matches above, loose matches on Subject: below --
2013-03-27  6:03 Mike Dilger
2013-03-29 17:23 ` David Sterba

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=20130323001201.2bbbb817@natsu \
    --to=rm@romanrm.ru \
    --cc=ask@develooper.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox