From: Gerald Hopf <gerald.hopf@nv-systems.net>
To: Roman Mamedov <rm@romanrm.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: "-d single" for data blocks on a multiple devices doesn't work as it should
Date: Tue, 24 Jun 2014 23:48:54 +0200 [thread overview]
Message-ID: <53A9F246.2040509@nv-systems.net> (raw)
In-Reply-To: <20140624170236.28d5bfa9@natsu>
On 24.06.2014 13:02, Roman Mamedov wrote:
> If you want to join multiple devices with a per-file granularity (so
> that a single file is wholely stored on one given device), check out
> the FUSE filesystem called mhddfs; I wrote an article about it some
> time ago: https://romanrm.net/mhddfs
Thank you very much for this excellent recommendation. I had never heard
of this layered "filesystem" before. And I have to admit, I was
initially quite skeptical of your mhddfs recommendation, because of...
well... FUSE :-)
But I read your article and the mhddfs documentation and it is exactly
the solution I had in mind (where trouble on one of the disks does never
ever affect data on other disks). mhddfs performance is also great,
130MB/s at only 50% load on one of the cpu's cores - it does only seem
to be limited by the disk and not by the CPU or FUSE.
Thanks again. I will now use mhddfs for my backups. And even though I'm
now not using btrfs for my backups, having a perfectly working backup
solution will make it much more likely for me to use BTFS on my main
disk array once the btrfs RAID5/6 support is slightly more complete :-)
Thanks again,
Gerald
next prev parent reply other threads:[~2014-06-24 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 10:42 "-d single" for data blocks on a multiple devices doesn't work as it should Gerald Hopf
2014-06-24 11:02 ` Roman Mamedov
2014-06-24 21:48 ` Gerald Hopf [this message]
2014-06-24 11:45 ` Duncan
2014-06-24 21:51 ` Gerald Hopf
2014-06-25 2:20 ` Austin S Hemmelgarn
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=53A9F246.2040509@nv-systems.net \
--to=gerald.hopf@nv-systems.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.net \
/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.