That explains it all BSDfan666!!!
and here's real-time, living proof, to what you just said and with links you posted.
I just used my usual command to restore but this time I am using ARCH first:
Code:
cat /12/PcBSD-Partiton-dd-By-FreeBSD.gz.* | gzip -dc | dd of=/dev/sda3
I never done this before under ARCH "I open another TERMINAL and ran TOP".
Within one minute I get:
Quote:
|
Kernel panic - not syncing: Out of memory and no killable processes...
|
I running this on the Gigabyte GA-880GA-UD3H mb, Phem-965 processor with DDR3 8GB1600MHz DUAL Viper. Unbelievable!!! My P3's was more than enough all along and never gave me these kinds of issues.
That goes to show, you can turn top on with BSD but not LINUX when using this kind of command. I never knew this until now.
After pulling the plug I tried again, but with-out turning anything on as usual and it replaced it even faster:
Code:
ARCH-2009 - 1,504,432,145,920 bytes - 150GB = 1851sec = 30min - 1/2 hour - 81 MB/s
I always view ARCH as a great dd,split tool with-out the hassle. I use split to save large files to MsDos partitions but I'm about to start saving to UFS and use ZFS. BLOCKS are fast but now I see why we can trust BSD a whole lot more. If this was reverse my first kernel panic ever could have destroyed all that I worked on in a heart-beat.
THANK-YOU
edit:: I thought it was a problem but it did work just fine.