Yes CIFS(well I have been told that officially it is now called SMB, but whatever), no I am not sharing with ESXi, VMs are on ssds.Smb, ya lost me there, as in CIFS? VMware doesnt support that as a stg protocol, there must be a mixup?
Yes CIFS(well I have been told that officially it is now called SMB, but whatever), no I am not sharing with ESXi, VMs are on ssds.Smb, ya lost me there, as in CIFS? VMware doesnt support that as a stg protocol, there must be a mixup?
GOTCHA, so you have those VM's on SSD's and they are local datastores to ESXi? If so you should really see the value in getting those ssd's in FreeNAS as well and running on NFS/iSCSI shared/clustered datastore. If you just have one host maybe not as big a deal but fun to experiment with.Yes CIFS(well I have been told that officially it is now called SMB, but whatever), no I am not sharing with ESXi, VMs are on ssds.
Fair enough, I am used to LONG NAS uptimes, this one is shorter due to co-lo maint but I've had them up for 1000+ days no issues.
[root@nas-lvco-pr01] ~# uptime
5:39PM up 277 days, 1:21, 1 user, load averages: 0.44, 0.44, 0.48
If and outage happens lmore frequently than the time I do major maint/upgrades I have to seriously reconsider my stg strategy.
Thin provisioning (I find) doesn't seem to reclaim space once used due to fragmentation. That said, this problem could be a lack of knowledge on my partThick provision on ESXi + compression on ZFS nicely trims it down to what you are using only. I guess thin provisioning has the same effect, but somehow it gives me the warm and fuzzies.
No, I think you're right ... Which means you have one more good reason to put your datastores on zfs instead of attaching themm to ESXi.Thin provisioning (I find) doesn't seem to reclaim space once used due to fragmentation. That said, this problem could be a lack of knowledge on my part
That is a relevant point. I have a pair of 80GB S3500's as directly attached ESXi datastores. I have my pfSense and FreeNAS VMs stored there (I mirror the vmdk's via their respective OS). All of the other VMs are stored on a mirrored ZFS set of SM843T's.Well, for example, if I decide to go to FreeNAS 10, when I do the upgrade, I don't want to have to take everything else offline.
Recently I upgraded a Ubuntu 14.04 VM to 16.04, and it failed catastrophically. I had backups, but I didn't want it to take everything else down.
I had recent issues with mythbuntu also, same deal.
I guess what I am saying is, the majority of times I need to bring a VM down are due to my own fault when trying to implement features or upgrades as opposed to an inherent problem with the platforms involved.
I am serving the home though, so I have a higher tolerance for problems than a production environment.