Hi Vicinius,
Thank you for your kind analysis.
Responses to your questions follow:
- The setting was sync=standard in the original samples.
- I have two 1TB NVME drives striped for the SLOG. You can see the
utilization on NVD1
- The pool is 65 TB is nize, with 4 tb (6%) used today.
Once upon a time, David Johnson said:
> Since our cluster is colocated in the power company's data center, if we
> see power loss we have much bigger problems.
Heh, you'd think that... but experience has taught me otherwise.
--
Chris Adams
___
Users
Hi David, as an advise. You should not set sync=disabled on TrueNAS. Doing that
you’re considering every write as async, and if you have a powerless you’ll
have data lost.
There are some conservatives that state that you should do the opposite:
sync=always, which bogs down the performance, but
I would consider using smaller templates .Also, give it a try with iSCSI.
Best Regards,Strahil Nikolov
On Wed, Jul 13, 2022 at 3:10, Pascal D wrote: I
have experienced the same performance problem in creating new template or
creating new stateful image from template. I have traced it to
I have experienced the same performance problem in creating new template or
creating new stateful image from template. I have traced it to the use of
qemu-img convert which is very very slow.
Currently a template creation on my setup, takes around 29m for a 45G image
when a simple copy over NF
Short answer: No.
Long answer: TrueNAS doesn't support pNFS yet (or at least does not
advertise that support), and they are having stability issues with some of
the other NFS enhancements they have brought in from BSD.
On Tue, Jul 12, 2022 at 3:31 PM Strahil Nikolov
wrote:
> Are you using pNFS
Are you using pNFS ?
Best Regards,Strahil Nikolov
On Tue, Jul 12, 2022 at 14:21, David Johnson
wrote: ___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privac
7 matches
Mail list logo
