9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bruce Ellis <brucee@chunder.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] fossil question
Date: Mon, 24 May 2004 14:59:19 +1000	[thread overview]
Message-ID: <40B18127.3030807@chunder.com> (raw)
In-Reply-To: <ee9e417a04052321474b7a047f@mail.gmail.com>

sorry, i read 'reasonable close' as 'reasonably close'.
they are all ~0.

Russ Cox wrote:

> the idea is that each block has a start and end epoch.
> start is the epoch it was created in, and end is the epoch
> that it was unlinked from the tree.  once the system has tossed
> or archived the snapshots up through the close epoch, the block
> can be reused.  precise accounting isn't necessary as long as
> the close epoch is correct.  when a block isn't yet closed it has
> a close epoch of ~0.  that's why i asked.
>
> what does the epoch command print?  maybe the epoch isn't
> moving forward as it should.  this can happen if a scan of the
> file system turns up trees from earlier epochs.  the epoch command
> prints them out along with suggested clri messages that would
> remove them.
>
> if the epoch command prints clris of /archive, it means the
> archiver hasn't finished yet-- just wait.  if it prints clris of old
> /snapshot trees, run them and try epoch again.
>
> one more thing.  fossil doesn't keep a precise accounting of
> blocks that might have been made free by moving the epoch forward.
> the df command rescans the disk to update the count if necessary.
> that's why df is so slow.  the original df didn't do this, but it's been
> this way for more than a year.  if you do not have a call to
> cacheCountUsed inside fsysDf in 9fsys.c, then df is printing a
> (perhaps gross) underestimate.
>
> russ
>
>


  reply	other threads:[~2004-05-24  4:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-24  0:14 Bruce Ellis
2004-05-24  2:22 ` Russ Cox
2004-05-24  4:28   ` Bruce Ellis
2004-05-24  4:47     ` Russ Cox
2004-05-24  4:59       ` Bruce Ellis [this message]
2004-05-24  5:19         ` Russ Cox
     [not found] <e1912b6dcca61d19ae435ec37a36817d@hamnavoe.com>
2004-05-24 15:56 ` Russ Cox
2004-05-24 22:13   ` Bruce Ellis
2004-05-24 22:25     ` Russ Cox
2004-05-24 23:07       ` Bruce Ellis
2004-05-24 23:32         ` Russ Cox
2004-05-25  2:08       ` Bruce Ellis
2004-05-25  2:08         ` Kenji Okamoto
2004-05-25  2:12           ` boyd, rounin
2004-05-25  2:36             ` Kenji Okamoto
2004-05-25  2:46               ` Kenji Okamoto
2004-06-07  6:47                 ` Kenji Okamoto
2004-06-07 13:36                   ` Russ Cox
2004-06-07 13:38                     ` Fco. J. Ballesteros
2004-05-25  2:21           ` Bruce Ellis
2004-05-25  2:33             ` Kenji Okamoto
2004-05-25  2:50               ` Bruce Ellis
2004-05-25 14:22         ` ron minnich
2004-05-25  8:31   ` Richard Miller
2004-05-25 21:28     ` Russ Cox
2004-05-26  5:05       ` lucio
2004-05-26 10:04         ` Bruce Ellis
2004-05-26 15:19           ` ron minnich
2004-05-26  8:05       ` Richard Miller
  -- strict thread matches above, loose matches on Subject: below --
2004-05-17 12:31 Fco.J.Ballesteros

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=40B18127.3030807@chunder.com \
    --to=brucee@chunder.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).