Search results

Okay, so here's my personal opinion about storage setup for home use. Keep it simple! ZFS is your friend here and any kind of pass-through just makes it more error prone. I've gone through multiple types of storage setups for my home lab and my current setup (Proxmox +ZFS) is by far the...

Glad it works for you. If you've got more questions, keep em coming;)

Okay, you're not crazy :D I just copied your setup and got the exact same result! I don't know what exactly is causing this but it's related to Ubuntu or the NFS version running on Ubuntu. It's simply ignoring the GID, it's only looking at the UID. Change the UID on both systems so they match...

Make sure your mountpoint also has g+rw . btw. I'm pretty sure this is not an ACL problem...

I'm not using acls myself so I can neither confirm nor deny that. But from reading the man page I think this is not necessary or the issue.

Try sharing to your local subnet rw=@192.168.200.0/24 or just set sharenfs=on. If I remember correctly you don't need the @ if you're sharing to a single host. Edit: From: https://linux.die.net/man/5/exports

How does your "sharenfs" option for tank/test look like ? It's definitely a permission problem.

That's true. For availability you would definitely run a virtual fileserver. But I doubt that many of us home users have a proxmox cluster running:D Edit: @EinsGehtNoch: As for your NFS troubles, try this. on proxmox: create a group that should be able to access files from an nfs share...

I think you misunderstood what I was trying to say. My point was that it is not necessary to put Virtual Fileserver on top of proxmox. Lets not forget, it's just Debian with a pve enabled kernel. And since it has already most of the packages installed you would need for a basic fileserver...

This is also possible. But adds another layer to your data that is not really necessary. If your Fileserver-VM breaks that data is gone. However if you just use your native filesystem (ZFS etc.) to store your data you can only really lose it due to a Hardware failure. On top of that you can just...

Overkill...maybe, depends on what you are trying to achieve. Permissions and NFS can be a pain. The most common gotcha is a UID/GID mismatch. I don't know how you've set it up but if you try to access an NFS share with user X that exists on both systems, that user must also have the same...

I guess that makes sense for an enterprise product :D. But maybe you could add a checkbox/dropdown in the installer to switch either repository on or off. Just a thought.

Thanks! The "No-Subscription" repo was missing. Thought that was in the sources.list.d/ like the enterprise repo. Any reason why this isn't the default configuration ? Or do I just have a wonky install ?!

I'm currently switching from your option 2 to 1 because it makes things a lot simpler and more manageable. I'm using a combination of NFS and autofs for filesystem access between host and VMs. If you're using ZFS you can simply set the sharenfs option on a dataset and mount it wherever you need.

Sorry for hijacking this old thread, but I've got the "same" problem. I've got a fresh install of pve 4.4.1 where I get this when I try to install ZED. [100] % sudo apt-get install zfs-zed Reading package lists... Done Building dependency tree Reading state information... Done Package...