From: Vester Thacker <vester.thacker@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan 9 server controls impaired and steps taken before
Date: Sun, 15 May 2005 02:11:50 +0900 [thread overview]
Message-ID: <32a656c2050514101155984a58@mail.gmail.com> (raw)
In-Reply-To: <ca7c4b96ac0a7fc6925a4ab34af47573@ar.aichi-u.ac.jp>
On 5/14/05, arisawa@ar.aichi-u.ac.jp <arisawa@ar.aichi-u.ac.jp> wrote:
>
> It seems fossil (at least in Jan. and Feb. of this year) locked the
> file service during "snap" and "snap -a".
> Does this continue?
I am not sure, but I am on Day 4 of the initial snap. I'm not sure how
long I need to wait until I consider the current installation process
a failure. Perhaps 12 more days of waiting and I'll call it quits.
Btw I have a 40 GB fossil and a 210GB venti running on an AMD64
machine. There is approximately 300 Mb of files on the fossil. I have
dma turned on. My hard disk is an ATA 133 w/ 16Mb of cache. I don't
understand *why* it takes so long for a snap to complete.
Sorry if I come off as appearing frustrated about the wait, but I am
*frustrated* about this.
This isn't something you can recommend your friends to try; or even
present to a crowd during an Expo.
-vester
next prev parent reply other threads:[~2005-05-14 17:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 1:43 [9fans] Plan 9 server controls impaired and steps taken before failure Vester Thacker
2005-05-10 1:50 ` andrey mirtchovski
2005-05-10 21:28 ` Bruce Ellis
2005-05-10 23:14 ` [9fans] Plan 9 server controls impaired and steps taken before andrey mirtchovski
2005-05-11 0:33 ` Vester Thacker
2005-05-13 16:26 ` Russ Cox
2005-05-13 21:29 ` arisawa
2005-05-14 17:11 ` Vester Thacker [this message]
2005-05-14 18:03 ` Russ Cox
2005-05-14 22:06 ` arisawa
2005-05-14 22:33 ` Russ Cox
2005-05-16 6:10 YAMANASHI Takeshi
2005-05-16 9:04 ` Richard Miller
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=32a656c2050514101155984a58@mail.gmail.com \
--to=vester.thacker@gmail.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).