From: "Paul Taysom" <Paul_Taysom@novell.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] 9p2k, fsync
Date: Thu, 8 Feb 2001 10:46:03 -0700 [thread overview]
Message-ID: <sa8278f7.052@prv-mail20.provo.novell.com> (raw)
Tsync: This way there be dragons.
The next thing you'll be asking for is byte range locks and then
locks that can survive crashes and then something to coordinate
updates to multiple files and then away to back it up . . . . . .
If you want ACID let's look at away of providing for it within the context
of the a simple file protocol.
Ideas for sync:
1. Battery backed static RAM for the more resent requests like NetApp.
2. A volume that does write through or flush on close.
I agree that databases have gotten way out of hand but is there away
within the spirit of Plan 9 to provide ACID? Sync does not meet the
requirement.
Paul Taysom
>>> nemo@gsyc.escet.urjc.es 02/08/01 07:03AM >>>
: Hey? No disagreement that it's a fileserver issue, but I should also
: be able to ask the file server to sync the data associated with a
: particular FID.
That's a question I have. I understand it can be done from its
console, but is there any way to ask 9pcfs for an inmediate sync
through the network?
And another one. Any plans to make the future fs kernel do software
mirrowing on ide disks?
next reply other threads:[~2001-02-08 17:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 17:46 Paul Taysom [this message]
2001-02-08 21:49 ` Dan Cross
-- strict thread matches above, loose matches on Subject: below --
2001-02-09 0:08 nemo
2001-02-09 18:37 ` Boyd Roberts
2001-02-08 22:27 forsyth
2001-02-09 18:43 ` Boyd Roberts
2001-02-09 21:37 ` Boyd Roberts
2001-02-08 14:03 nemo
2001-02-08 12:50 Laura Creighton
2001-02-08 20:03 ` Dan Cross
2001-02-08 6:26 rob pike
2001-02-08 6:24 rob pike
2001-02-08 22:08 ` Dan Cross
2001-02-08 1:32 rob pike
2001-02-08 5:43 ` Dan Cross
2001-02-08 1:15 Russ Cox
2001-02-08 6:01 ` Dan Cross
2001-02-08 7:28 ` Nikolai Saoukh
2001-02-09 17:32 ` Boyd Roberts
2001-02-10 2:06 ` Dan Cross
2001-02-07 19:14 jmk
2001-02-08 1:02 ` Dan Cross
[not found] <rob@plan9.bell-labs.com>
2001-02-07 15:23 ` rob pike
2001-02-07 18:42 ` Scott Schwartz
2001-02-08 1:19 ` Dan Cross
2001-02-08 9:43 ` Douglas A. Gwyn
2001-02-07 15:06 jmk
2001-02-07 18:16 ` Scott Schwartz
2001-02-09 17:15 ` Boyd Roberts
2001-02-07 7:05 Scott Schwartz
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=sa8278f7.052@prv-mail20.provo.novell.com \
--to=paul_taysom@novell.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).