<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.thibble.org/goomba/index.php?action=history&amp;feed=atom&amp;title=Proxmox_NFS_Configuration</id>
	<title>Proxmox NFS Configuration - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.thibble.org/goomba/index.php?action=history&amp;feed=atom&amp;title=Proxmox_NFS_Configuration"/>
	<link rel="alternate" type="text/html" href="https://wiki.thibble.org/goomba/index.php?title=Proxmox_NFS_Configuration&amp;action=history"/>
	<updated>2026-07-29T01:14:59Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.42.1</generator>
	<entry>
		<id>https://wiki.thibble.org/goomba/index.php?title=Proxmox_NFS_Configuration&amp;diff=36&amp;oldid=prev</id>
		<title>T20A02: Created page with &quot;NFS Configuration for Proxmox  When Using Truenas as a disk source for proxmox VM&#039;s I ran into issues with the write speed of the disks stored on the NFS share, mounted on the Truenas Scale server. The issue seemed to be related to the file syncing properties of ZFS, and was allowing strong read speeds, but abysmal write speeds, as it was attempting to write sync all of the data being written from the VM OS.  Note: For some instances, such as using TrueNAS Scale, I had t...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.thibble.org/goomba/index.php?title=Proxmox_NFS_Configuration&amp;diff=36&amp;oldid=prev"/>
		<updated>2024-08-31T03:09:58Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;NFS Configuration for Proxmox  When Using Truenas as a disk source for proxmox VM&amp;#039;s I ran into issues with the write speed of the disks stored on the NFS share, mounted on the Truenas Scale server. The issue seemed to be related to the file syncing properties of ZFS, and was allowing strong read speeds, but abysmal write speeds, as it was attempting to write sync all of the data being written from the VM OS.  Note: For some instances, such as using TrueNAS Scale, I had t...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;NFS Configuration for Proxmox&lt;br /&gt;
&lt;br /&gt;
When Using Truenas as a disk source for proxmox VM&amp;#039;s I ran into issues with the write speed of the disks stored on the NFS share, mounted on the Truenas Scale server. The issue seemed to be related to the file syncing properties of ZFS, and was allowing strong read speeds, but abysmal write speeds, as it was attempting to write sync all of the data being written from the VM OS.&lt;br /&gt;
&lt;br /&gt;
Note: For some instances, such as using TrueNAS Scale, I had to call the zfs command with the full &lt;br /&gt;
&lt;br /&gt;
path /usr/sbin/zfs&lt;br /&gt;
&lt;br /&gt;
Here&amp;#039;s a basic outline of how you might achieve&lt;br /&gt;
&lt;br /&gt;
First, you&amp;#039;ll need to identify the dataset associated with your NFS share. You can do this by listing the datasets:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
zfs list&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Look for the dataset that corresponds to your NFS share.&lt;br /&gt;
&lt;br /&gt;
Modify the Sync Property: Once you&amp;#039;ve identified the dataset, you can modify its sync property to change the sync behavior. The available options for the sync property are typically standard, always, or disabled. To set the sync property to asynchronous (disabled):&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
zfs set sync=disabled pool_name/dataset_name&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Replace pool_name/dataset_name with the actual name of your dataset.&lt;br /&gt;
&lt;br /&gt;
For example:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
zfs set sync=disabled tank/my_nfs_share&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Verify Changes: After making this change, you can verify the updated property settings&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
zfs get sync pool_name/dataset_name&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
This command will display the current value of the sync property for the specified dataset.&lt;br /&gt;
&lt;br /&gt;
Remember, adjusting the sync property to asynchronous might improve performance in certain scenarios, but it also introduces a higher risk of data loss in case of unexpected power loss or system crashes. Ensure that you understand the implications before making such changes, and always have proper backups and safeguards in place for your data.&lt;br /&gt;
&lt;br /&gt;
Please replace pool_name/dataset_name with the actual names of your pool and dataset when executing these commands to modify the sync property accordingly.&lt;/div&gt;</summary>
		<author><name>T20A02</name></author>
	</entry>
</feed>