From: Ram Ramesh <rramesh2400@gmail.com>
To: Kai Stian Olstad <raid+list@olstad.com>
Cc: Drew <drew.kay@gmail.com>, antlists <antlists@youngman.org.uk>,
Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: Best way to add caching to a new raid setup.
Date: Wed, 2 Sep 2020 13:17:36 -0500 [thread overview]
Message-ID: <d48e1365-a86c-bdcd-fd2a-d65767fbf2fa@gmail.com> (raw)
In-Reply-To: <20200901170158.acaq54zxfeaiasdk@olstad.com>
On 9/1/20 12:01 PM, Kai Stian Olstad wrote:
> On Tue, Sep 01, 2020 at 11:12:40AM -0500, Ram Ramesh wrote:
>> I really wished overlay fs had a nice merge/clean feature that will allow us
>> to move overlay items to underlying file system and start over the overlay.
> You should check out mergerfs[1], it can merge multiple directories together
> on different disks and you can transparently move files between them.
> Mergerfs have a lot of other features too that you might find useful.
>
> [1] https://github.com/trapexit/mergerfs/
>
Kai,
Thanks. It is interesting. However, my starting point for this
discussion was improving performance and this one seems a bit backward
as it uses FUSE. I still think it is a good step. So I will learn a bit
more to see if I can use it.
Regards
Ramesh
next prev parent reply other threads:[~2020-09-02 18:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16cee7f2-38d9-13c8-4342-4562be68930b.ref@verizon.net>
2020-08-28 2:31 ` Best way to add caching to a new raid setup R. Ramesh
2020-08-28 3:05 ` Peter Grandi
2020-08-28 3:19 ` Ram Ramesh
2020-08-28 15:26 ` antlists
2020-08-28 17:25 ` Ram Ramesh
2020-08-28 22:12 ` antlists
2020-08-28 22:40 ` Ram Ramesh
2020-08-28 22:59 ` antlists
2020-08-29 3:08 ` R. Ramesh
2020-08-29 5:02 ` Roman Mamedov
2020-08-29 20:48 ` Ram Ramesh
2020-08-29 21:26 ` Roger Heflin
2020-08-30 0:56 ` Ram Ramesh
2020-08-30 15:42 ` Roger Heflin
2020-08-30 17:19 ` Ram Ramesh
2020-09-11 18:39 ` R. Ramesh
2020-09-11 20:37 ` Roger Heflin
2020-09-11 22:41 ` Ram Ramesh
2020-08-29 0:01 ` Roger Heflin
2020-08-29 3:12 ` R. Ramesh
2020-08-29 22:36 ` Drew
2020-09-01 16:12 ` Ram Ramesh
2020-09-01 17:01 ` Kai Stian Olstad
2020-09-02 18:17 ` Ram Ramesh [this message]
2020-09-14 11:40 ` Nix
2020-09-14 14:32 ` Ram Ramesh
2020-09-14 14:48 ` Roger Heflin
2020-09-14 15:08 ` Wols Lists
2020-08-31 19:20 ` Nix
2020-08-28 17:46 ` Roman Mamedov
2020-08-28 20:39 ` Ram Ramesh
2020-08-29 15:34 ` antlists
2020-08-29 15:57 ` Roman Mamedov
2020-08-29 16:26 ` Roger Heflin
2020-08-29 20:45 ` Ram Ramesh
2020-08-30 22:16 ` Michal Soltys
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=d48e1365-a86c-bdcd-fd2a-d65767fbf2fa@gmail.com \
--to=rramesh2400@gmail.com \
--cc=antlists@youngman.org.uk \
--cc=drew.kay@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=raid+list@olstad.com \
/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;
as well as URLs for NNTP newsgroup(s).