From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] FS to skip/put-together duplicate files
Date: Tue, 14 Aug 2007 09:16:45 -0400 [thread overview]
Message-ID: <087b06bcf86bfd29df76102d98e19b1f@coraid.com> (raw)
In-Reply-To: <bf64731d0708122032r15da2773w489891c0fdd68d9f@mail.gmail.com>
> 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.
>
this is always cited as the "killer functionality" of venti. essentially it trades cpu time
for disk space. however, the couple of times where a concrete venti solution was
discussed (seperating attachments into seperate files, e.g. for de-duping), it was
deemed to be slower because attachments need to be split out to be recognized
as the same. (9fans.net/archive/2005/10 and 9fans.net/archive/2005/11/1).
i wonder about this today with such large disks.
does anyone have an example of a case where compression and uniquing are required?
- erik
next prev parent reply other threads:[~2007-08-14 13:16 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
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 [this message]
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=087b06bcf86bfd29df76102d98e19b1f@coraid.com \
--to=quanstro@coraid.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).