From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: [9fans] now for something completely devfs :)
Date: Wed, 9 Jul 2003 09:42:02 -0600 [thread overview]
Message-ID: <Pine.LNX.4.44.0307090906010.8112-100000@fbsd.cpsc.ucalgary.ca> (raw)
Now I have a venti, I'm keeping score, emailing it to myself every morning
(thanx to nemo's suggestions!) and am ready to embark on something that'll
break the machine completely! I decide to create a devfs mirror.
The fossil installation page on the wiki gives some instructions, but the
main part is missing -- how to write the first disk to the second one?
In the hardware RAID world, there are utilities provided for copying a hard
drive 'en masse' to others to create the mirror. With devfs I'm supposed to
do it myself.
But what do I copy? The entire drive (dd -if /dev/sdC0/data -of /dev/sdD0/data)?
Partition by partition? The wiki says:
If you already have a fossil and want to add another disk to
mirror it, you can setup the mirror as said before, start your
fossil and while you are using it, use dd(1) to copy the first
device to the new one. Since writes go to all devices but reads
are performed just by the first device as long as it works it
can be done this way.
but what does 'other one' mean here? am I supposed to do something like:
dd -if /dev/sdC0/isect -of /dev/fs/isect
? (ok, I try that -- I echo a file to sdD0's isect, run the command, it
takes much longer than normal, completes, I run cmp on the two drives
-- they're not the same.)
Another thing: I should *not*, repeat *not* mirror 9fat with devfs, right?
Because if I do the machine becomes unbootable. MBR... shows up, but 9load
is nowhere to be found.
also: how do I know if one of my /dev/fs/ mirrored disks has crashed? I
mean, without rebooting :)
andrey
next reply other threads:[~2003-07-09 15:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 15:42 andrey mirtchovski [this message]
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
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=Pine.LNX.4.44.0307090906010.8112-100000@fbsd.cpsc.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).