correct BUT if you don't do that you won't have an exact copy, and if
you have "so so" sectors, you might not be able to fix that on
a "regular" copied drive. Also, some of these copy utilities do not
know why something is in a different order.
(older copy protection worked like that, part of the trick was to stick
a key in a fragmented file, that you read "sparse".. BUT if someone
copied that
key, the copy process would exactly do what you describe, de-fragment
it, and consequently destroy the key.
Oh and nothing to be horrified about, just don't write to the old
drive, dd for sure doesn' as long as the drive is used in the if.
Also, you can mount the drive as root, and work with it as non root
and it won't write on it. that's 2 layers right there.
If you just want copies of the files and not an exact copy of the drive
.. why not just copy all the files/directories you need?
On 4/23/20 12:15 PM, Jon Elson wrote:
On 04/23/2020 12:10 PM, Rafael Skodlar wrote:
Bravo. I'm horrified reading recommendations to use dd for cloning
files on storage devices. dd copies fragmented files as is so you are
messing new drive for performance issues from the get go.
Yes, this is true. But, if you copy the partitions with cp, rsync or
whatever, you get a more efficient file system, but grub will not be
able to immediately load the kernel. You then have to re-run grub
to link to where the kernel is now placed in the file system. This is
doable, but a bit complicated.
Jon
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
