Bug #9102
zfs should be able to initialize storage devices
Start date:
2018-02-13
Due date:
% Done:
100%
Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Description
The first access to a disk block can incur a performance penalty on some platforms (e.g. AWS's EBS, VMware VMDKs). Therefore it is recommended that volumes be "thick provisioned", where supported by the platform (VMware). Thick provisioning is time consuming and often is ignored. If the thick provision step is omitted, customers will see suboptimal performance until we have written to all parts of the LUN. ZFS should be able to initialize any unused storage to remove any first-write penalty that exists.
History
Updated by Electric Monk about 1 year ago
Updated by - Status changed from New to Closed
- % Done changed from 0 to 100
git commit 094e47e980b0796b94b1b8f51f462a64d246e516
commit 094e47e980b0796b94b1b8f51f462a64d246e516
Author: George Wilson <george.wilson@delphix.com>
Date: 2018-04-25T22:29:05.000Z
9102 zfs should be able to initialize storage devices
Reviewed by: John Wren Kennedy <john.kennedy@delphix.com>
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed by: Pavel Zakharov <pavel.zakharov@delphix.com>
Reviewed by: Prakash Surya <prakash.surya@delphix.com>
Approved by: Richard Lowe <richlowe@richlowe.net>
Updated by Electric Monk about 1 year ago
git commit 2b7e4143e3543c9086e5a53ddea2cbc235ebada0
commit 2b7e4143e3543c9086e5a53ddea2cbc235ebada0
Author: Matthew Ahrens <mahrens@delphix.com>
Date: 2018-04-26T22:47:30.000Z
9102 zfs should be able to initialize storage devices (fix mapfile)