All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: ceph, slow (cheap) and fast (expensive) storage?
Date: Wed, 09 Jun 2010 16:55:34 +0200	[thread overview]
Message-ID: <4C0FAB66.6030003@wpkg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1006081047120.15202@cobra.newdream.net>

Am 08.06.2010 19:51, Sage Weil wrote:
> On Tue, 8 Jun 2010, Tomasz Chmielewski wrote:
>> I'd like to build a cluster for storing large amounts of data.
>>
>> The cluster would consist of slow (cheap) storage and fast (expensive)
>> storage.
>>
>> I would like to migrate data from fast (expensive) storage to slow (cheap)
>> storage if it wasn't accessed for, say, 6 months.
>>
>> Would ceph somehow help me achieve that?
>
> We don't currently have that functionality.  In principle it's certainly
> something the system could do, and the underlying storage architecture
> lends itself to that:

Hmm, since quite recently, Linux kernel has FS-Cache, which:

	This facility is a general purpose cache for network
	filesystems, though it could be used for caching other things
	such as ISO9660 filesystems too.


I wonder if it could work with ceph and/or traditional filesystems, too?


-- 
Tomasz Chmielewski
http://wpkg.org

  reply	other threads:[~2010-06-09 14:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08 10:30 ceph, slow (cheap) and fast (expensive) storage? Tomasz Chmielewski
2010-06-08 10:53 ` Wido den Hollander
2010-06-08 12:04   ` Tomasz Chmielewski
2010-06-08 13:13     ` ales-76
2010-06-08 12:41 ` Thomas Mueller
2010-06-08 18:03   ` Sage Weil
2010-06-08 17:51 ` Sage Weil
2010-06-09 14:55   ` Tomasz Chmielewski [this message]
2010-06-09 15:11     ` Wido den Hollander

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=4C0FAB66.6030003@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@newdream.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.