Correction:
On 2002 December 23 at 14:58 I wrote:
32-bit I/O [...] made no difference in speed whether it was on or
off. The Debian hdparm readme said the same thing: that 32bit-I/O
usually does nothing for drive performance.
I looked again and it turns out that this information came
I will try it again tonight before bedtime. I figure it will take several
hours to duplicate my 40 GB drive. Which block size do you think I should
use to improve the speed? Is bigger better?
It should take 1-2 hours, if you have all the right hdparm settings.
Using Debian's
For those of you who don't mind something a tad
proprietary, Symantec's Ghost works rather well with
ext2/3 partitions and I ghosted my 20 to a 60 and a
few days later to an 80 and all I had to do each time
was use my Linuxcare CD to run lilo and I could be up
and running again. Total time for the
On 12/24/02 06am, Dexter Graphic wrote:
I will try it again tonight before bedtime. I figure it will take several
hours to duplicate my 40 GB drive. Which block size do you think I should
use to improve the speed? Is bigger better?
It should take 1-2 hours, if you have all
Dexter,
Your drive is still taking way too long. Use hdparm if necessary to set
(turn on) the speedier features of your drive. You should be able to read
and write your drive a whole lot faster than 4 hours.
Ralph
Well, that would be nice but I tested all the options you suggested
.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Bob Miller
Sent: Friday, December 13, 2002 15:49
To: [EMAIL PROTECTED]
Subject: Re: [Eug-lug]Mirroring a drive (all partitions and the MBR)
Dexter Graphic wrote:
I will try it again tonight before bedtime. I figure
On Thu, 12 Dec 2002, Dexter Graphic wrote:
Any suggestions on how I can mirror (duplicate onto an identical
drive) my fancy 3 distribution and 8 partition GNU/Linux system?
Would dd if=/dev/hda of=/dev/hdb work? If so, do I have to run
it from a boot floppy so that no partitions are
Horst wrote:
I am not sure if the block size needs to match the granulariy of the
device, i.e. would a partial block been read and written?
Yes. dd does the right thing.
Also I don't know how the funny stuff in /proc is handled by dd ?
/proc does not exist on disk -- it's created on the
Thanks for the tips, Horst and KBob. I tried running a disk duplication
last night before I went to bed but this morning I was disappointed to
find it hadn't worked.
I had mistakenly issued the command dd if=/dev/hda of=/hdb and ended
up filling my root partition completely so that dd aborted
Sounds like a job for toms root boot :) or the linux care cd!
Ive used bs=4M, I dont know what the limit is, but bs=1024M is 1G... I dont
know if that would work, or if you need 1G ram to acually do block sizes that
big when you test it... let us know!
Jamie
On Friday 13 December 2002
clip from web:
Which block size do you think I should
use to improve the speed? Is bigger better?
Something is odd on efn -- 2 or 3 of my postings never made it (either out
or back in), so I am clipping form web archives.
clip of 1st lost:
..., one more on the issue of larger block size: it
Dexter Graphic wrote:
I will try it again tonight before bedtime. I figure it will take several
hours to duplicate my 40 GB drive. Which block size do you think I should
use to improve the speed? Is bigger better?
It should take 1-2 hours, if you have all the right hdparm settings.
For my
12 matches
Mail list logo
