9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Georg Lehner <jorge-plan9@magma.com.ni>
To: 9fans@cse.psu.edu
Subject: [9fans] fossil+plan9: disk full revisited
Date: Wed, 22 Nov 2006 01:24:47 +0100	[thread overview]
Message-ID: <871wnw49bk.fsf@jorgito.magma.com.ni> (raw)

Hello!

It seems that this year I am the one who stumbled over the infamous
"cacheAllocBlock: xxx1 disk is full" situation.  No problem: I
formatted and started over :-0


The setup is a 100GB plan9 partition with about 14GB fossil and the
rest venti, set up for confidence and performance tests of
Plan9/fossil+venti in order to evaluate it for production use as a
fileserver in the internal network at my work, with some Linux and a
lot of Windows users.

For a start, I copied a disk image with about 18GB from a Linux server
with u9fs to the Plan9 file server, which obviously choked fossil.

Two questions:

- Would it help to write blocks to venti and free them on fossil, if a
  snapshot is taken in the middle of a transfer of one file bigger
  than the whole fossil partition?

- How much would fossil have to be altered, to make it automatically
  write blocks to venti when only a certain amount of blocks is free
  anymore.

While timed snapshots are really a nice thing for archiving, this
feature maybe would make fossil+venti practically maintenance free.

Regards,

        Jorge-León


             reply	other threads:[~2006-11-22  0:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22  0:24 Georg Lehner [this message]
2006-11-22 11:23 ` Robert Raschke
2006-11-23  2:05 ` Dave Eckhardt
2006-11-29 21:10   ` Georg Lehner
2006-11-29 22:34     ` geoff

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=871wnw49bk.fsf@jorgito.magma.com.ni \
    --to=jorge-plan9@magma.com.ni \
    --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).