From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] fossil
Date: Thu, 4 Jun 2009 15:25:47 -0400 [thread overview]
Message-ID: <3f9f8b75b4a7b780b3533cf218205cda@quanstro.net> (raw)
In-Reply-To: <42bc252f1ccd5b7887be54121d677cb6@terzarima.net>
On Thu Jun 4 05:11:02 EDT 2009, forsyth@terzarima.net wrote:
> anyone else ever seen things like this from fossil? it seems a bit wayward...
>
> # on the fossil console, after `disk full' returned in errors:
>
> main: df
> main: 10,046,783,488 used + 35,180,756,598,784 free = 6,431,293,440 (156% used)
> main: snapclean 3600
> main: df
> main: 3,000,909,824 used + 3,430,383,616 free = 6,431,293,440 (46% used)
i suspect the free should be printed as a signed quanity. ☺
the management of fl->nused seems to permit a hole
(which isn't new) that could prevent fl->nused from being
decremented while still removing stuff from the fl in doRemoveLink.
perhaps i've misread the code.
it would be interesting to see what the difference between
the output of df would be if cacheCountUsed could be
asked to return both the cached fl->nused and also compute
it as it does if the epochs don't match.
it would be even more interesting if they differ, if resetting
fl->nused with the newly computed value just does the right
thing.
- erik
next prev parent reply other threads:[~2009-06-04 19:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 9:29 Charles Forsyth
2009-06-04 19:25 ` erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-17 16:16 [9fans] Interoperating between 9legacy and 9front Noam Preil
2024-05-18 19:08 ` [9fans] fossil Richard Miller
2005-01-03 18:37 Bruce Ellis
2005-01-03 18:51 ` Russ Cox
2005-01-04 17:42 ` Russ Cox
2004-06-12 3:12 Russ Cox
2004-03-20 2:27 David Presotto
2003-04-15 5:26 Andrew
2003-04-15 15:12 ` Russ Cox
2003-04-15 21:00 ` Andrew
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=3f9f8b75b4a7b780b3533cf218205cda@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).