In mergerfs you can access the xattrs of the file folder and they will show their origin branch. Just check the mergerfs docs. Also I not sure if these xattrs are visible via samba or nfs.
Posts by subzero79
-
-
No, it won’t work.
The plugin fork did a lot of changes internally.
The old ssh method relied a lot on systemd. How it was mechanized is documented in a blog post which was mentioned in the fork. You can follow that post and organize the units manually. Or you can use the other ssh method which uses drop bear at initramfs.
I do not use it since I have omv as virtual machine so I can automate unlock something like `ssh pve qm terminal $vmid`
I have to check the plugin error, look like is missing the db section entry, that should be added at install of the plugin.
-
No didn’t port the plugin. I created a branch to use crypttab, simplifying the process alittle bit but I didn’t get any feedback
-
I haven't dont an iso install in a while, do you remember if the hostname was setup autmatically or there is a prompt an you entered plethi.local?
Because if the installer is appending local automatically to the hostname in the db, that means there might be something to correct there as you can see the error triggers in a new install.
-
But should OMV keep changing the MAC it would be a little awkward doing this repeatedly due to other configuration tied to the MAC address that my set-up requires (open ports, etc).
It shouldn't change, MAC address is tied to the hardware you cannot change it, you can spoof it temporally as those changes are lost at reboot.
-
It shouldn’t change on upgrade, odd issue there. But why don’t you paste the new address in the dhcp list of the router.
Omv doesn’t provide in the web ui a field Mac change.
Other than that you should check netplan configuration at /etc/netplan And check netplan docs if they provide MAC address configuration.
-
How did you install omv?
-
UUID mount naming and device mount was used at the beginning.
Eventually(maybe in omv4?) changed due to users complaining not having friendly names , because of that they were unable to associate the physical disk/partition to the filesystem in an explorer or terminal.
Now it mounts first option using the fs label and if not present using the device name(id) as seen by the kernel.
This behavior is hard coded and cannot be changed using omv env variables.
-
Yeah the hostname should be only allowed characters for hostname.
Check in general the hostname and domain don’t put dots in the hostname.
-
Is complaining about the domain maybe. Try set up the hostname same as plethi and domain as lan.
I have to check the code if there is validation in salt that does not allow .local as domain. Maybe is to avoid problems with avahi.
-
You can try and replicate the tree structure in a single disk by scripting. Generate those 27000 dirs with some contents take out mergers out of the equation. See if it behaves differently.
-
No, because in the webui there is no restart button for services that uses RPC. all rpc service:methods are listed here.
https://github.com/openmediava…penmediavault/engined/rpc
votdev might correct me and might be another place to look.
Basically you would have to use FTP-setSettings disabled, mark dirty, apply, setSettings-enabled mark dirty apply. Not sure if you can do that in several requests.
In the internal backend api there is wrapper for systemd systemctl which is used for restarting services, but is not exposed.
-
Shouldn’t be any problem. With omvextras you can install the same pve kernel which includes already the zfs modules.
-
So my question is more, how do we point the container to the .env file? How do we declare the .env? So that the container uses those values.
You can use a mount bind to pass the whole folder to the container that has the .env but what’s the point? The container will not read that file automatically. The .env file is used to store values that are you going to keep repeating inside the yaml file. A compose file can have many different containers, if each of them need access to a common path or using same PUID .env saves the tedious work of changing every string, instead is just changed at .env just once.
-
There’s two different environmental variables in discussion here.
First in yaml the environment keywords generates the lists all ev for the running container.
Second the .env file is loaded previous reading of the compose yaml and sources all variables that are going to be rendered in the yaml file. Those are the dollar sign variables in the compose file. Those variables are not passed to the container. As mentioned before the .env file goes along the compose file in the same folder.
So for example in your running container if you exec bash into it and run echo $MEDIA nothing will output as that was a variable used to construct the yaml file.
-
Hey....long time no see
Any idea where I can find the orphaned data?
There is no recycle when deleting shared folders through the web UI, only when deleting through samba and only IF is enabled. So as i see it data is gone.
You can run the classic du -h --max-depth=1 in /srv/dev-..... to show the size layout in the first level.
-
Why are interested in boot repair ? This is not a boot disk. What you’re trying to recover is the partition layout table. Please run gdisk see if it detects a gpt partition.
-
Looks like the partition rescue mentioned in that article isn't around anymore but I was able to use "testdisk" and got it kinda working
What do you mean with this? maybe gdisk is not installed by default but the tool is still available
apt install gdisk
-
Unless the pcie slots are explicitly disabled in bios. I have no idea if that’s possible I guess it depends on the motherboard. I know you can disable sata ports.
If you connect an active network cable do the leds show activity?
-
Try and login via ssh. Does the partition now shows with blkid?
