From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Changelogs & Patches?
Date: Tue, 6 Jan 2009 11:19:56 -0500 [thread overview]
Message-ID: <129b32f691c934d77d2454071d09a6fd@quanstro.net> (raw)
In-Reply-To: <14ec7b180901060622q2a179705g53c7fe62e70ee90a@mail.gmail.com>
very interesting post.
> this is an example of the design decision difference between
> fossil/venti and zfs: venti commits storage permanently and everything
> becomes a snapshot, while the designers of zfs decided to create a
> two-stage process introducing a read-only intermediary between the
> original data and a read-write access to it independent of other
> clients.
a big difference between the decisions is in data integrety.
it's much easier to break a fs that rewrites than it is a worm-based
fs. even if the actual media are the same. and a broken rewriting
fs is much harder to recover. russ wrote up a bit on recovering one
good venti from an old copy and a damaged current venti. this
same approach, (basically fs | fs') works for any worm fs.
> from a remote node. if i create a zfs cloned volume i need to arrange
> an iscsi method of access from a remote node. both nfs and iscsi have
> a host of nasty settings that need to be correct on both ends in order
> for things to work right. i can never hope to export an nfs share
> outside my DMZ.
>
> i don't see a solution to this problem: the unix world is committed to
> nfs and a bit less so to iscsi. i'm more of a 9p guy myself though, so
> i listed it as a complaint.
oh, my perfect chance to shill aoe! how to configure aoe on plan 9
echo bind /net/ether0>/dev/aoe/ctl
now for the hard part
# (this space intentionally left blank.)
- erik
next prev parent reply other threads:[~2009-01-06 16:19 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 15:27 Venkatesh Srinivas
2008-12-22 15:29 ` erik quanstrom
2008-12-22 16:41 ` Charles Forsyth
2008-12-25 6:34 ` Roman Shaposhnik
2008-12-25 6:40 ` erik quanstrom
2008-12-26 4:28 ` Roman Shaposhnik
2008-12-26 4:45 ` lucio
2008-12-26 4:57 ` Anthony Sorace
2008-12-26 6:19 ` blstuart
2008-12-27 8:00 ` Roman Shaposhnik
2008-12-27 11:56 ` erik quanstrom
2008-12-30 0:31 ` Roman Shaposhnik
2008-12-30 0:57 ` erik quanstrom
2009-01-05 5:19 ` Roman V. Shaposhnik
2009-01-05 5:28 ` erik quanstrom
2008-12-22 17:03 ` Devon H. O'Dell
2008-12-23 4:31 ` Uriel
2008-12-23 4:46 ` Nathaniel W Filardo
2008-12-25 6:50 ` Roman Shaposhnik
2008-12-25 14:37 ` erik quanstrom
2008-12-26 13:27 ` Charles Forsyth
2008-12-26 13:33 ` Charles Forsyth
2008-12-26 14:27 ` tlaronde
2008-12-26 17:25 ` blstuart
2008-12-26 18:14 ` tlaronde
2008-12-26 18:20 ` erik quanstrom
2008-12-26 18:52 ` tlaronde
2008-12-26 21:44 ` blstuart
2008-12-26 22:04 ` Eris Discordia
2008-12-26 22:30 ` erik quanstrom
2008-12-26 23:00 ` blstuart
2008-12-27 6:04 ` Eris Discordia
2008-12-27 10:36 ` tlaronde
2008-12-27 16:27 ` Eris Discordia
2008-12-29 23:54 ` Roman Shaposhnik
2008-12-30 0:13 ` hiro
2008-12-30 1:07 ` erik quanstrom
2008-12-30 1:48 ` Charles Forsyth
2008-12-30 13:18 ` Uriel
2008-12-30 15:06 ` C H Forsyth
2008-12-30 17:31 ` Uriel
2008-12-31 1:58 ` Noah Evans
2009-01-03 22:03 ` sqweek
2009-01-05 5:05 ` Roman V. Shaposhnik
2009-01-05 5:12 ` erik quanstrom
2009-01-06 5:06 ` Roman Shaposhnik
2009-01-06 13:55 ` erik quanstrom
2009-01-05 5:24 ` andrey mirtchovski
2009-01-06 5:49 ` Roman Shaposhnik
2009-01-06 14:22 ` andrey mirtchovski
2009-01-06 16:19 ` erik quanstrom [this message]
2009-01-06 23:23 ` Roman V. Shaposhnik
2009-01-06 23:44 ` erik quanstrom
2009-01-08 0:36 ` Roman V. Shaposhnik
2009-01-08 1:11 ` erik quanstrom
2009-01-20 6:20 ` Roman Shaposhnik
2009-01-20 14:19 ` erik quanstrom
2009-01-20 22:30 ` Roman V. Shaposhnik
2009-01-20 23:36 ` erik quanstrom
2009-01-21 1:43 ` Roman V. Shaposhnik
2009-01-21 2:02 ` erik quanstrom
2009-01-26 6:28 ` Roman V. Shaposhnik
2009-01-26 13:42 ` erik quanstrom
2009-01-26 16:15 ` Roman V. Shaposhnik
2009-01-26 16:39 ` erik quanstrom
2009-01-27 4:45 ` Roman Shaposhnik
2009-01-21 19:02 ` Uriel
2009-01-21 19:53 ` Steve Simon
2009-01-24 3:15 ` Roman V. Shaposhnik
2009-01-24 3:36 ` erik quanstrom
2009-01-26 6:21 ` Roman V. Shaposhnik
2009-01-26 13:53 ` erik quanstrom
2009-01-26 16:21 ` Roman V. Shaposhnik
2009-01-26 17:37 ` erik quanstrom
2009-01-27 4:51 ` Roman Shaposhnik
2009-01-27 5:44 ` erik quanstrom
2009-01-21 20:01 ` erik quanstrom
2009-01-24 3:19 ` Roman V. Shaposhnik
2009-01-24 3:25 ` erik quanstrom
2009-01-20 6:48 ` Roman Shaposhnik
2009-01-20 14:13 ` erik quanstrom
2009-01-20 16:19 ` Steve Simon
2009-01-20 23:52 ` andrey mirtchovski
2009-01-21 4:49 ` Dave Eckhardt
2009-01-21 6:38 ` Steve Simon
2009-01-21 14:02 ` erik quanstrom
2009-01-26 6:16 ` Roman V. Shaposhnik
2009-01-26 16:22 ` Russ Cox
2009-01-26 19:42 ` Roman V. Shaposhnik
2009-01-26 20:11 ` Steve Simon
2008-12-27 7:40 ` Roman Shaposhnik
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=129b32f691c934d77d2454071d09a6fd@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.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 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).