From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] now for something completely devfs :)
Date: Wed, 9 Jul 2003 15:52:51 -0700 [thread overview]
Message-ID: <2c2226061eedb01d1a6fd20d2e42a947@collyer.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0307090906010.8112-100000@fbsd.cpsc.ucalgary.ca>
I think the paragraph on the wiki would be clearer like this:
If you already have a fossil and want to add another disk to mirror
it, you can setup the mirror as said before, with the original fossil
device (possibly a partition) being mirrored by the new disk, start
your fossil and while you are using it, use dd(1) to copy the fossil
device to the mirror device or partition. Since writes go to all
devices in the mirror but reads are performed just by the first device
(as long as it has no read errors), the copy can be made this way with
relative safety. Races are still possible, since dd might read a
block from the fossil device, fossil might change it and write it to
both devices (original fossil and mirror) and then dd might write the
now-stale block to the mirror, so it's safer to make the copy when
fossil (and venti, if you mirror it) are idle. This might require
booting your file server off another standalone Plan 9 file & cpu
server.
How do you know if a disk in a mirror has died? The kernel should
print I/O-error messages on the console. devfs should cope until you
can shut the system down and replace the dying disk. With modern
disks, I/O errors are generally a sign of degradation: the disk has
forwarded as many bad sectors as it can and now the reserved bad
sector areas are full.
next prev parent reply other threads:[~2003-07-09 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 15:42 andrey mirtchovski
2003-07-09 16:01 ` andrey mirtchovski
2003-07-09 17:06 ` Fco.J.Ballesteros, nemo
2003-07-09 17:19 ` andrey mirtchovski
2003-07-09 18:43 ` Fco.J.Ballesteros, nemo
2003-07-09 22:52 ` Geoff Collyer [this message]
2003-07-09 23:02 ` Geoff Collyer
2003-07-09 23:32 ` Scott Schwartz
2003-07-09 23:44 ` boyd, rounin
2003-07-10 8:10 ` Fco.J.Ballesteros, nemo
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=2c2226061eedb01d1a6fd20d2e42a947@collyer.net \
--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).