I run kubernetes with nfs shares. On kubernetes I run owncloud. owncloud writes/reads data with user and group www-data (gid 33) on a mounted nfs share. But unraid is changing the owncloud-files' user and groups always to 99 when running owncloud. 

 

So I added

"/mnt/user/owncloud-files" -async,no_subtree_check,fsid=110 *(sec=sys,rw,insecure,anongid=100,anonuid=33,all_squash)

to unraid linux' /etc/exports

 

That works until the next time I stop the array. After turning on the array again the anonuid is 99 in unraid's /etc/exports.

 

This is suuuper annoying. Any idea what to change so that the anonuid stays 33?

 

Many thanks

Heikki

You would have to set up a script to run at array start (user scripts) that makes the necessary adjustments

21 minutes ago, Heikki Heer said:

unraid linux

is in RAM. The OS is unpacked fresh from the archives into RAM at each boot and runs completely in RAM. Think of it as firmware.

 

Any edits to OS must be reapplied after boot.

Thanks. I could have thought of that myself. Thanks for the hint.

 

For anyone else with a similar problem:

 

I copied the /etc/exports file into a folder on the array. So everytime the array has startet a scheduled shellscript is run:

 

 

#!/bin/bash
cat /mnt/user/folder/exports > /etc/exports

 

In my opinion a very crude way. But it seems to work fine.