9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Christopher Nielsen <cnielsen@pobox.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Fossil Questions
Date: Wed, 23 Jul 2003 12:23:42 -0700	[thread overview]
Message-ID: <20030723192342.GF63873@cassie.foobarbaz.net> (raw)

Is it just me or does fossil not clear the write buffer
after 'snap -a' is performed?

I am in the process of archiving my music collection to
fossil+venti, executing 'snap -a' when the write buffer
gets close to full. I was expecting to be able to just
start writing to the buffer once the archival snapshot
finished. Instead, it seems that I have to 'flfmt -v ...'
the write buffer and restart fossil. This is a bit
cumbersome when you have a fileserver that boots from
fossil+venti. Also, from what I have experinced so far,
fossil gets very cranky and does not recover gracefully
when the write buffer is filled.

I know people are on vacation and such, and I am more than
happy to dive into the code to address this. Before I do,
I want to make sure the behavior I am seeing is accurate
and the behavior I expect is desired.

That said, I must say the system is quite robust from a
data safety standpoint. I've been through repeated crashes
and have not lost any data that was archived to venti.
Very nice work guys.

--
Christopher Nielsen
"They who can give up essential liberty for temporary
safety, deserve neither liberty nor safety." --Benjamin Franklin


             reply	other threads:[~2003-07-23 19:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 19:23 Christopher Nielsen [this message]
2003-07-24  3:11 ` Christopher Nielsen
  -- strict thread matches above, loose matches on Subject: below --
2003-01-08  6:45 [9fans] 4th edition file server available Russ Cox
2003-01-29  1:37 ` [9fans] Fossil questions John Packer
2003-01-29  2:02   ` Russ Cox
2003-01-30  0:17     ` John Packer
2003-01-30 16:58       ` Tharaneedharan Vilwanathan
2003-01-30 17:22         ` Russ Cox

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=20030723192342.GF63873@cassie.foobarbaz.net \
    --to=cnielsen@pobox.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).