From: g.pavelcak@comcast.net
To: 9fans@cse.psu.edu
Subject: [9fans] Changing disks on fs64 server
Date: Sat, 15 Jul 2006 12:23:10 +0000 [thread overview]
Message-ID: <071520061223.13070.44B8DE2E0001A0CE0000330E2207021053050E0C040A900E9FD209@comcast.net> (raw)
I updated my kernel and copydev appears to be working. Just one question. Is it surprising that this type of copy is really slow? It said it was going to copy 6 million plus blocks. It's now (8:20 AM Eastern) done just over 5 million blocks. I started about 1:30 PM yesterday. Does that mean I have really slow disks or is that normal? I'm copying from IDE to a mirrored scsi device: copydev h0 {w2w3}, as Geoff suggested.
Thanks.
Greg
next reply other threads:[~2006-07-15 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-15 12:23 g.pavelcak [this message]
2006-07-25 23:12 ` geoff
-- strict thread matches above, loose matches on Subject: below --
2006-07-14 0:13 Gregory Pavelcak
2006-07-14 1:10 ` geoff
2006-07-13 20:50 g.pavelcak
2006-07-13 23:35 ` geoff
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=071520061223.13070.44B8DE2E0001A0CE0000330E2207021053050E0C040A900E9FD209@comcast.net \
--to=g.pavelcak@comcast.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).