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:28:09 +1000 [thread overview]
Message-ID: <40B179D9.9050601@chunder.com> (raw)
In-Reply-To: <ee9e417a04052319222f6a4b80@mail.gmail.com>
no, the epochs seem random (777, 1083, etc) - the current
epoch is 3442. the first N blocks are all unreachable
and then it starts thinning out.
at 98% now, and clri of an epoch frees nothing.
Russ Cox wrote:
>>if i run "fossil/flchk -f" i get thousands of
>>bfrees which all belong to long gone epochs.
>>i'm very reluctant to do an update as fossil
>>is the root filesystem and if i screw it up
>>i'm screwed - i'm also reluctant to do a few
>>thousand bfrees.
>
>
> do they have reasonable close numbers?
next prev parent reply other threads:[~2004-05-24 4:28 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 [this message]
2004-05-24 4:47 ` Russ Cox
2004-05-24 4:59 ` Bruce Ellis
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=40B179D9.9050601@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).