From: "YAMANASHI Takeshi" <9.nashi@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] FS to skip/put-together duplicate files
Date: Mon, 13 Aug 2007 12:32:06 +0900 [thread overview]
Message-ID: <bf64731d0708122032r15da2773w489891c0fdd68d9f@mail.gmail.com> (raw)
In-Reply-To: <40b85517d889fadc8df2c782817f6bef@quanstro.net>
how about mounting venti-backed fossil files from a linux as an AoE drives?
vblade on sources exports the plan 9 file and the aoe driver for linux
does the mounting.
Venti would be compressing and condensing duplicated blocks to a single block.
I'm not sure if same files are boundaried in same manner to each other though.
On 8/10/07, erik quanstrom <quanstro@quanstro.net> wrote:
> > I'm host a lot of web applications which share 99% of their code.
> > Disk space is not the issue, but bandwidth on remote backup.
> > So my idea is to let an filesystem automatically link together
> > equal files in the storage, but present them as separate ones.
> > Once an file gets changed, it will be unlinked/copied automatically.
> >
> > Is there already such an filesystem ?
>
> no.
>
> however there are updatedb/compactdb which can be used to
> create a list of changed files and replica/applylog which can
> be used to apply them.
>
> i used these tools to copy history from one kenfs to a new one.
> i actually used cphist (/n/sources/patch/saved/cphist) and not
> applylog.
>
> you could also use the log on the generating machine to build
> a mkfs archive and compress that, ftp it and apply it on the
> other end.
>
> - erik
>
--
YAMANASHI Takeshi
next prev parent reply other threads:[~2007-08-13 3:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 11:39 Enrico Weigelt
2007-08-10 11:51 ` Gabriel Diaz
2007-08-10 12:26 ` erik quanstrom
2007-08-13 3:32 ` YAMANASHI Takeshi [this message]
2007-08-13 12:01 ` erik quanstrom
2007-08-13 13:43 ` Francisco J Ballesteros
2007-08-13 13:52 ` erik quanstrom
2007-08-13 14:40 ` Francisco J Ballesteros
2007-08-14 13:16 ` erik quanstrom
2007-08-14 13:57 ` Steve Simon
2007-08-14 14:13 ` erik quanstrom
2007-08-14 15:02 ` David Leimbach
2007-08-14 16:18 ` Uriel
2007-08-14 16:25 ` erik quanstrom
2007-08-15 0:27 ` Uriel
2007-08-15 0:42 YAMANASHI Takeshi
2007-08-15 0:47 ` erik quanstrom
2007-08-15 0:49 YAMANASHI Takeshi
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=bf64731d0708122032r15da2773w489891c0fdd68d9f@mail.gmail.com \
--to=9.nashi@gmail.com \
--cc=9fans@cse.psu.edu \
/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).