From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Reliability of fossil
Date: Wed, 22 Oct 2003 17:09:10 +0200 [thread overview]
Message-ID: <0f2e986de625824a35852cc937ca00ba@plan9.escet.urjc.es> (raw)
In-Reply-To: <8CFD66E7-0491-11D8-A23F-000393A941BC@ar.aichi-u.ac.jp>
[-- Attachment #1: Type: text/plain, Size: 141 bytes --]
how did you reconstruct the file server? copying the arenas back?
Did you start with a brand new fossil?
Is this fossil the one breaking?
[-- Attachment #2: Type: message/rfc822, Size: 3703 bytes --]
From: arisawa@ar.aichi-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] Reliability of fossil
Date: Wed, 22 Oct 2003 22:13:38 +0900
Message-ID: <8CFD66E7-0491-11D8-A23F-000393A941BC@ar.aichi-u.ac.jp>
Hello,
My comments about reliability of fossil.
I have two fossil server. One is for home network, another is for
Internet.
CASE fossil for home network
That works perfectly fine. No trouble since the first installation
term% ls /n/dump/*
d-r-xr-xr-x M 29 adm adm 0 Jan 18 2003 /n/dump/2003/0118
d-r-xr-xr-x M 29 adm adm 0 Jan 19 2003 /n/dump/2003/0119
d-r-xr-xr-x M 29 adm adm 0 Jan 19 2003 /n/dump/2003/0119.1
d-r-xr-xr-x M 29 adm adm 0 Jan 20 2003 /n/dump/2003/0120
d-r-xr-xr-x M 29 adm adm 0 Feb 4 2003 /n/dump/2003/0204
d-r-xr-xr-x M 29 adm adm 0 Feb 6 2003 /n/dump/2003/0206
...
d-r-xr-xr-x M 29 adm adm 0 Oct 19 22:25 /n/dump/2003/1019
d-r-xr-xr-x M 29 adm adm 0 Oct 20 07:46 /n/dump/2003/1020
d-r-xr-xr-x M 29 adm adm 0 Oct 20 22:18 /n/dump/2003/1020.1
d-r-xr-xr-x M 29 adm adm 0 Oct 21 22:35 /n/dump/2003/1021
d-r-xr-xr-x M 29 adm adm 0 Oct 22 09:03 /n/dump/2003/1022
term%
CASE fossil for Internet
My computers are placed at my office of my university.
Three of my machines were dead at 8 August because of typhoon.
Windows were open and the machines were drenched!
File server and CPU server were alive.
So I reconstructed file server to be auth+venti+fossil server.
The system continued working without any trouble until 30 September.
My system, ar.aichi-u.ac.jp (with alias plan9.aichi-u.ac.jp) has been
in service for educational purpose. A massive amount of accesses
comes from students, specially at every Tuesday.
The day, 30 September, was the first Tuesday of this semester.
From that day, my fossil falls into broken state at every Tuesday.
I suspected hardwares because they were old and I replaced them
with new one. However even after the replacement, fossil continues
getting
into trouble at every Tuesday.
Now I have added new machine that is based on kfs for the services to
students.
I appreciate the effort of Russ. Fossil is really fine. But it is
desired to
test under hard condition.
Kenji Arisawa
next prev parent reply other threads:[~2003-10-22 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 13:13 arisawa
2003-10-22 15:09 ` Fco.J.Ballesteros [this message]
2003-10-23 8:00 ` arisawa
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=0f2e986de625824a35852cc937ca00ba@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).