How is TRIM handled when cloning a disk with dd?

sweber

11/19/22, 3:50 PM

The TRIM command allows an OS to inform an SSD which sectors contain data, and which are free. This allows the disk to re-use free sectors internally and improves wear leveling.

Now, if an SSD is cloned to anoher via dd, each single sector is copied to the target disk. However, dd does not know if the content of the sectors is actually data, or unused. That is, it can not send a TRIM command to the target disk. To my understanding, the target disk has to consider EACH written sector as used.

The only way around would be if the used/free information is somehow stored in the sectors themself, and so is copied by dd to the new disk.

So, how is it done? Is there a problem?

1 + 2

hard-drive

cloning

trim

Tom Yan

11/19/22, 5:46 PM

No problem. There's no *real* way to tell whether a block is mapped to actual / wanted data or not. You can at best mount all the filesystems on the clone and `fstrim` them all after cloning. (Although, `sparse` *might* help you avoid writing all-zero blocks...? That's technically irrelevant with whether the source block was TRIM'd before cloning though.)

NiKiZe

12/8/22, 2:03 PM

Yes there is a problem in that you have written to a disk and caused ware on it. Don't use dd with a SSD as target.

Score:0

Server

user10489

11/20/22, 12:15 AM

The TRIM standard states that reading a trimmed block gives undefined results. Some versions of trim will simulate returning a zeroed block when you read it, others may return the previous data, or some random data.

0 + 3

Michael Hampton

11/20/22, 12:32 AM

ACS-3 says the drive will report whether it does deterministic read after TRIM and whether such reads return zeroes. Most modern SSDs will do both.

sweber

11/20/22, 4:03 AM

That is not what I'm asking. My question is: dd blindly copies blocks from source to target. It does not know if a block is trimmed, and so does not tell the target disk. Finally, when cloning an empty disk with all trimmed blocks, you will end up with an empty target disk where each block is marked as used...

user10489

11/20/22, 4:41 AM

@sweber: that's not a question, that's the answer. And if you don't like that result, don't use dd. For instance, you could create a new fs on the new disk and copy with a tar pipe or something. Or use a fs clone utility that knows about filesystem free space and doesn't copy it.