chiark / gitweb /
import: also set NOCOW for gpt disk images
authorLennart Poettering <lennart@poettering.net>
Thu, 8 Jan 2015 00:25:40 +0000 (01:25 +0100)
committerLennart Poettering <lennart@poettering.net>
Thu, 8 Jan 2015 00:25:40 +0000 (01:25 +0100)
Given the write patterns on disk images, we better should turn COW off
for them. In particular as the file systems used inside the disk images
should do their own data integrity checks anyway and we don't need
multiple layers of it.


No differences found