From: Marc Joliet <marcec@gmx.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: Using Btrfs on single drives
Date: Sun, 15 Nov 2015 07:30:08 +0100 [thread overview]
Message-ID: <1900961.ItTdAumaJ1@thetick> (raw)
In-Reply-To: <pan$eeab5$356873bd$675c810f$20fe76ea@cox.net>
[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]
On Sunday 15 November 2015 04:01:57 Duncan wrote:
>audio muze posted on Sun, 15 Nov 2015 05:27:00 +0200 as excerpted:
>> I've gone ahead and created a single drive Btrfs filesystem on a 3TB
>> drive and started copying content from a raid5 array to the Btrfs
>> volume. Initially copy speeds were very good sustained at ~145MB/s and
>> I left it to run overnight. This morning I ran btrfs fi usage
>> /mnt/btrfs and it reported around 700GB free. I selected another folder
>> containing 204GB and started a copy operation, again from the raid5
>> array to the Btrfs volume. Copying is now materially slower and slowing
>> further...it started at ~105MB/s and after 141GB has slowed to around
>> 97MB/s. Is this to be expected with Btrfs of have I come across a bug
>> of some sort?
>
>That looks to /me/ like native drive limitations.
>
[Snip nice explanation]
I'll just add that I see this with my 3TB USB3 HDD, too, but also with my
internal HDDs. Old drives (the oldest I had were about 10 years old) also had
this problem, only scaled appropriately (the worst was something like 40/60
GB/s min./max.).
You can also see this very nicely with scrub runs (I use dstat for this):
they start out at the max., but gradually slow down as they progress.
HTH
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-15 6:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-14 10:43 Using Btrfs on single drives audio muze
2015-11-14 11:09 ` Goffredo Baroncelli
2015-11-14 16:35 ` Duncan
2015-11-15 3:27 ` audio muze
2015-11-15 4:01 ` Duncan
2015-11-15 6:30 ` Marc Joliet [this message]
2015-11-25 7:20 ` Russell Coker
2015-11-26 16:27 ` Duncan
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=1900961.ItTdAumaJ1@thetick \
--to=marcec@gmx.de \
--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