francisaugusto
Contributor
- Joined
- Nov 16, 2018
- Messages
- 153
Ok, hear me out because this is a bit weird...
I have two pools: /mnt/mainpool and /mnt/backup
The `/mnt/backup` is mounted as a datastore on an ESXI host so that I perform backups. I started to use ghettoVCB to backup my VMs.
I noticed recently that out of the blue my nfs shares get painfully slow. They are mounted from `/mnt/mainpool`. Even booting a Raspberry Pi from an NFS share gets incredibly slow.
I couldn't find anything on my logs, but I realized today that, while I experienced this, ghettoVCB was backing up a VM. The backup should be saved on `/mnt/backup`, but still ALL my shares on other disks were super slow. I killed the job, and bang, shares started to be responsive again.
What could be the cause of this? I mean, nothing is being written to my main pool, or read. Why suddenly my whole NFS gets slow? And are there any remediation for this?
I have another ESXI host and I experienced painfully slow VMs there, when they were on NFS, even if they have always run fine. I suspect it was the same problem. The way ghettoVCB works - if I got that right - was to snapshot a VM to my backup pool. Could it be that snapshotting a working VM to another NFS share makes things slow? I see that some of those operations take 6-7 hours, as the machine is very active.
Any tips?
I have two pools: /mnt/mainpool and /mnt/backup
The `/mnt/backup` is mounted as a datastore on an ESXI host so that I perform backups. I started to use ghettoVCB to backup my VMs.
I noticed recently that out of the blue my nfs shares get painfully slow. They are mounted from `/mnt/mainpool`. Even booting a Raspberry Pi from an NFS share gets incredibly slow.
I couldn't find anything on my logs, but I realized today that, while I experienced this, ghettoVCB was backing up a VM. The backup should be saved on `/mnt/backup`, but still ALL my shares on other disks were super slow. I killed the job, and bang, shares started to be responsive again.
What could be the cause of this? I mean, nothing is being written to my main pool, or read. Why suddenly my whole NFS gets slow? And are there any remediation for this?
I have another ESXI host and I experienced painfully slow VMs there, when they were on NFS, even if they have always run fine. I suspect it was the same problem. The way ghettoVCB works - if I got that right - was to snapshot a VM to my backup pool. Could it be that snapshotting a working VM to another NFS share makes things slow? I see that some of those operations take 6-7 hours, as the machine is very active.
Any tips?