From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] lucio-
Date: Mon, 4 Mar 2002 16:10:43 -0800 [thread overview]
Message-ID: <20020305001326.CF6AA19A9C@mail.cse.psu.edu> (raw)
It depends what you mean by ``bogs down the fileserver''. Depending
on how many dirty blocks are in the mag disk cache, triggering a dump
to worm disks makes the file server completely unresponsive to
requests from the network for anywhere from a few seconds to a couple
of minutes while the copy-on-write fork of the file system is
performed. Thereafter, it can take quite a while (depending on the
speed of worm writing) to complete the dump, but performance of the
file server is essentially unaffected.
So warning people in advance of a dump would give them time to take a
short break and get coffee or coke without feeling annoyed. I have
occasionally wished for a more direct means of notifcation than mail,
perhaps the ability to write a short message after the time in a
vismon window or pop up an acme window containing a brief message.
next reply other threads:[~2002-03-05 0:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 0:10 geoff [this message]
2002-03-05 17:07 ` Dan Cross
2002-03-11 10:05 ` Luis Fernandes
2002-03-12 7:17 ` [9fans] lucio- now: student projects Martin C.Atkins
-- strict thread matches above, loose matches on Subject: below --
2002-03-05 1:42 [9fans] lucio- Russ Cox
2002-01-10 15:31 rob pike
2002-01-10 11:07 forsyth
2002-01-10 1:36 okamoto
2002-01-10 13:52 ` Boyd Roberts
2002-01-09 7:06 okamoto
2002-01-09 5:41 geoff
2002-01-09 5:08 Russ Cox
2002-01-09 5:32 ` Lucio De Re
2002-01-09 6:01 ` Lucio De Re
2002-01-10 10:37 ` Bruce Janson
2002-03-04 21:14 ` Richard Uhtenwoldt
2002-01-09 3:06 Russ Cox
2002-01-09 4:49 ` Lucio De Re
2002-01-09 4:52 ` Lucio De Re
2002-01-09 10:58 ` Boyd Roberts
2002-01-09 16:01 ` Aharon Robbins
2002-01-09 1:04 okamoto
2002-01-08 18:01 Russ Cox
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=20020305001326.CF6AA19A9C@mail.cse.psu.edu \
--to=geoff@collyer.net \
--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).