Linux NILFS development
 help / color / mirror / Atom feed
From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org,
	leon-UvuJAy62EvlM7kwft8N7nw@public.gmane.org
Subject: Re: Dump tools for checkpoints
Date: Sun, 15 Mar 2009 22:58:35 +0900 (JST)	[thread overview]
Message-ID: <20090315.225835.27463578.ryusuke@osrg.net> (raw)
In-Reply-To: <20090313162609.GD7494-Tv691C15nu5348sJH/KcYBvVK+yQ3ZXh@public.gmane.org>

Hi,
On Fri, 13 Mar 2009 17:26:09 +0100, Leon Weber wrote:
> On 08.03.2009 14:39:16, Ryusuke Konishi wrote:
> > I've moved the replication feature to the top of todo list in our web
> > site ;)
> 
> Is replication really a feature that a file system should implement? I
> think it should be implemented one layer below the fs. If one needs a
> replicated file system, there are things like drbd (distributed
> replicated block device).

Yes, DRBD is another solution. I'm actually thinking it a possible
measure though we haven't yet evaluate for nilfs.  But as you know the
granularity differs from that of the checkpoint based solution.

Unless the checkpoint based solution doesn't have any merit, I think
the solution to be chosen depends on customer's (users') demand and
so-called service level.

Anyway you have a good point.  I should care not only rsync but also
drbd and other block layer solutions, and must find merits definitely.

> Of course, the file system should support being
> on a replicated device, though I don't really see a need to implement
> this on the fs layer, or am I missing anything?
> 
> Leon

In general, filesystems are said to have better opportunity to utilize
the knowledge for their metadata structures and consistency especially
for copy-on-write filesystems.

Those can efficiently extract delta by nature, and can drop
intermediate changes depending on required granularity.

Will it true with nilfs? - I don't know yet, but I think it's one of
the feature being worth of consideration.

Thanks,
Ryusuke Konishi

  parent reply	other threads:[~2009-03-15 13:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-01  0:57 Dump tools for checkpoints nilfs-MZZvbRqs/9F0RdzJJlgK+g
     [not found] ` <2883.84.133.202.72.1235869032.squirrel-lZV7jZi4TBeO2lRZCxuEEg@public.gmane.org>
2009-03-08  5:39   ` Ryusuke Konishi
     [not found]     ` <20090308.143916.113539820.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-03-12 15:26       ` Reinoud Zandijk
     [not found]         ` <20090312152618.GA25317-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2009-03-13 15:33           ` Ryusuke Konishi
2009-03-13 16:26       ` Leon Weber
     [not found]         ` <20090313162609.GD7494-Tv691C15nu5348sJH/KcYBvVK+yQ3ZXh@public.gmane.org>
2009-03-13 16:53           ` Gergely Gábor
2009-03-13 17:33           ` mail-MZZvbRqs/9F0RdzJJlgK+g
     [not found]             ` <3214.84.133.153.87.1236965583.squirrel-lZV7jZi4TBeO2lRZCxuEEg@public.gmane.org>
2009-03-16  0:57               ` Ryusuke Konishi
2009-03-15 13:58           ` Ryusuke Konishi [this message]
2009-03-13 16:42       ` nilfs-MZZvbRqs/9F0RdzJJlgK+g
     [not found]         ` <2893.84.133.153.87.1236962534.squirrel-lZV7jZi4TBeO2lRZCxuEEg@public.gmane.org>
2009-03-15 15:12           ` Ryusuke Konishi

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=20090315.225835.27463578.ryusuke@osrg.net \
    --to=ryusuke-sg5x7nla6pw@public.gmane.org \
    --cc=leon-UvuJAy62EvlM7kwft8N7nw@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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