From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] p9p venti sync?
Date: Tue, 16 Nov 2010 22:39:09 -0500 [thread overview]
Message-ID: <AANLkTimooTkgnwbS+QrdTn6Xo7FtD5h240VRk25NHM6b@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikKp0ycALR+wq3b9x3yBsjWFDJpGZR8O0xma0yZ@mail.gmail.com>
On Tue, Nov 16, 2010 at 10:19 PM, David Leimbach <leimy2k@gmail.com> wrote:
> On Tuesday, November 16, 2010, Russ Cox <rsc@swtch.com> wrote:
>> On Tue, Nov 16, 2010 at 5:43 PM, David Leimbach <leimy2k@gmail.com> wrote:
>>> I'm trying to figure out how to correctly sync a plan9port venti instance so
>>> I can start it back up again and have it actually function :-).
>>> using venti/sync doesn't appear to get the job done...
>>
>> It should. Not using venti/sync should work too since
>> vac etc all sync before hanging up. The flushicache/flushdcache
>> trick will make restarting a little faster, but it should not
>> be necessary for correctness and shouldn't even be
>> that much faster.
>
> I did a kill TERM... should the signal handler have cleaned up or was
> I supposed to send HUP?
There's no cleanup. The data's on disk after a sync RPC,
which is what venti/sync does and also what vac does when
it is done. Venti's writes are ordered so that the on-disk state
is always recoverable. Because of that, there's no explicit
shutdown: you just kill the server however you like.
Russ
next prev parent reply other threads:[~2010-11-17 3:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 22:43 David Leimbach
2010-11-17 0:32 ` Bakul Shah
2010-11-17 2:47 ` Russ Cox
2010-11-17 3:19 ` David Leimbach
2010-11-17 3:39 ` Russ Cox [this message]
2010-11-17 4:09 ` David Leimbach
2010-11-17 4:47 ` David Leimbach
2010-11-17 4:49 ` David Leimbach
2010-11-17 14:36 ` Russ Cox
2010-11-17 15:17 ` David Leimbach
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=AANLkTimooTkgnwbS+QrdTn6Xo7FtD5h240VRk25NHM6b@mail.gmail.com \
--to=rsc@swtch.com \
--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).