Lars Jensen
Explorer
- Joined
- Feb 5, 2013
- Messages
- 63
Hi
I'm trying to create a pool with a Intel P3700 NVMe as ZIL (probably the same issue with any NVMe/SSD and TRIM).
Reading https://www.freebsd.org/doc/handbook/zfs-advanced.html this can take a long time because of TRIM will run on the P3700. And it does, so the "GUI Storage menu" hangs and I see a CLI command run. I assume when the CLI command has finished the GUI Storage menu will become responsive again.
I've added tunable vfs.zfs.vdev.trim_on_init=0 and the pool gets created instant. The long wait is gone!
There a mention on https://www.freebsd.org/doc/handbook/zfs-advanced.html that states using vfs.zfs.vdev.trim_on_init=0 can be added to make creation go faster, if device "has already been secure erased".
Is it safe to use vfs.zfs.vdev.trim_on_init=0 (and wipe disk), or should I wait for TRIM to finish ?
P.S. TRIM is enabled by default with vfs.zfs.trim.enabled= 1
I'm trying to create a pool with a Intel P3700 NVMe as ZIL (probably the same issue with any NVMe/SSD and TRIM).
Reading https://www.freebsd.org/doc/handbook/zfs-advanced.html this can take a long time because of TRIM will run on the P3700. And it does, so the "GUI Storage menu" hangs and I see a CLI command run. I assume when the CLI command has finished the GUI Storage menu will become responsive again.
I've added tunable vfs.zfs.vdev.trim_on_init=0 and the pool gets created instant. The long wait is gone!
There a mention on https://www.freebsd.org/doc/handbook/zfs-advanced.html that states using vfs.zfs.vdev.trim_on_init=0 can be added to make creation go faster, if device "has already been secure erased".
Is it safe to use vfs.zfs.vdev.trim_on_init=0 (and wipe disk), or should I wait for TRIM to finish ?
P.S. TRIM is enabled by default with vfs.zfs.trim.enabled= 1