Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Jan 2017 08:28:50 -0700 (MST)
From:      Warren Block <wblock@wonkity.com>
To:        David Christensen <dpchrist@holgerdanske.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: FreeBSD 11.0-RELEASE-p7 i386 system drive imaging and migration
Message-ID:  <alpine.BSF.2.20.1701300827260.85129@wonkity.com>
In-Reply-To: <f44805f3-fd1c-e5e9-5d61-5360a3b1469a@holgerdanske.com>
References:  <df0c81d7-fd2b-852f-4007-5fb4b24100e0@holgerdanske.com> <86bmupg0gi.fsf@WorkBox.homestead.org> <2973d1ea-202f-60fa-2930-eec05b626cfb@holgerdanske.com> <alpine.BSF.2.20.1701292221150.71961@wonkity.com> <f44805f3-fd1c-e5e9-5d61-5360a3b1469a@holgerdanske.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Sun, 29 Jan 2017, David Christensen wrote:

>> Writing SSDs with dd is not good, limiting their wear leveling.
>
> That's why I used zcat rather than dd for writing to the cloned SSD. If/when 
> I know enough to use zfs send/ receive, that will be best.

zcat is no different than dd in this case.  When you write a binary 
image, the SSD can't tell which blocks are truly in use, because they 
have all been written.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1701300827260.85129>