Recent content by Steph007

I just have an uncontrollable urge to fiddle with everything :) It's honestly not a big deal and the only reason I asked is because most articles I could get my hands on claimed a 20 to 30% speed increase when using NFS4. My sysctl.conf is pretty stock , haven't changed anything specific and...

Hi There, Isn't NFS4 suppose to outperform NFS3 ? I've been running some tests and either and most likely I'm doing something wrong but it seems like NFS3 outperform NFS4 with at least 80%... Perhaps some optimization is required? Server config : /etc/exports; /home...

Here's my results using pvepeft... It also seems like my raid card cache isn't functioning since it requires a BDU / battery of some sorts which I'm guessing will improve my write speed quite a bit ? I'm also considering to change my RAID array from raid 6 to 10 which should give me a...

Hi There, I'm somewhat new to the whole virtualization scene but I do have a little linux experience under the belt. Anyway , I've build a small "NAS" containing my VM images which gets accessed by a proxmox PVE which is hosted on it's own separate hardware. I've configured NFS4 between my NAS...

Manually mounting the filesystem on the PVE also works fine.

The actual NFS server seems fine , I've managed to mount the same folder manually from another Centos host without any issues. mount -t nfs4 10.50.0.2:/ /mnt/nfs/ df |grep 10.50 10.50.0.2:/ 1338517504 295501824 1043015680 23% /mnt/nfs -steph

Yup , I actually just dropped the whole firewall and also disabled selinux on the Centos 7 NFS server.

I'm seeing the following error when I change to version 4. Mar 2 12:25:05 pve2 pvedaemon[9509]: create failed - mount error: mount.nfs: mounting 10.50.0.2:/home failed, reason given by server: No such file or directory Here's my config file: nfs: nas1 server 10.50.0.2 export...

Hi There, Is there any reason why Proxmox 4.1 doesn't give you the option to create an NFS4 mount? Not stable or will it be implemented in future releases? Anyway , the only info I could find were a guy asking the same question in 2012 running Proxmox 2.1.1. Apparently he got around the issue...